Use/Test Case #BB

Parameters in File Template and File Template Variants

Scenario
The purpose of this use case is to create a file submission and change the parameters dynamically using the
parameters tab. Also, a file template variant workbench can be used to get the parameters. The user can
adjust these values while creating the file submission.

DISCLAIMER: The steps described in the procedure steps below reflect sample
configuration/customizing, master, and transactional data (e.g., Agreement types, condition types,
material item numbers, customer numbers, etc.) as they exist in Vistex’s development/demonstration
system. SAP must substitute whatever valid configuration/customizing, master, and transactional
data they have created in the solution validation test system.

Note: When conducting this use-case, replace the <…> references throughout this use-case with the data in
the prerequisites.

Contents
Configuration Step 1: Configure Agreement Type................................................................................................3
Section 1.1 – Maintain Condition Table.............................................................................................................................3
Section 1.2 – Define Access Sequences.............................................................................................................................3
Section 1.3 – Maintain Condition Types............................................................................................................................3
Section 1.4 – Define Price Sheets......................................................................................................................................4
Section 1.5 – Maintain Condition Type Group...................................................................................................................5
Section 1.6 – Assign Condition Type to Condition Type Group..........................................................................................5
Section 1.7 – Maintain Number Ranges for Condition Contracts......................................................................................5
Section 1.8 – Create Condition Contract Type...................................................................................................................6
Section 1.9 – Define Number Ranges for Agreement........................................................................................................6
Section 1.10 – Create Agreement Type.............................................................................................................................6
Configuration Step 2: Configure File Template.....................................................................................................7
Section 2.1 – Create a File Template.................................................................................................................................7
Configuration Step 3: Configure File Template Variant.........................................................................................8
Section 3.1 – Create Number Range and Create a File Template Variant.........................................................................8
Configuration Step 4: Configure Submission Type...............................................................................................9
Section 4.1 – Create a Submission Type............................................................................................................................9
Exercise Step 1: Parameters in File Template....................................................................................................10
Step 1.1 – Create a File Submission.................................................................................................................................10
Step 1.2 – Upload Agreement using File Submission.......................................................................................................10
 Use/Test Case #BB

Exercise Step 2: Variants in File Template.........................................................................................................11

Step 2.1 – Get the Variant...............................................................................................................................................11
Step 2.2 – Create File Submission with Variant...............................................................................................................11
Step 2.3 – Upload Agreement using File Submission.......................................................................................................11

 Prerequisites - PQ_Parameters.csv and PQ_Variant.csv files.

June 2023 Page 2 of 11

 Use/Test Case #BB

Configuration Step 1: Configure Agreement Type

After this exercise, the user will be able to:

 Configure a Billback Agreement type.

Section 1.1 – Maintain Condition Table

In a condition table, the user defines the combination of fields for which the user can create
condition records.

1.1.1 Go to /IRM/IPSPRO
1.1.2 Create a new condition table by selecting IPSPRO > Incentive and Payback Module
> Basic Functions > Pricing Sales > Pricing Control  Define Condition Tables
1.1.3 Maintain the Table A966 with the Key fields: Agreement, Sales Organization,
Distribution Channel, Customer
1.1.4 Maintain the Table A967 with the Key fields: Agreement & Material

Section 1.2 – Define Access Sequences

The access sequence is a search strategy that the SAP System uses to search for condition
records valid for a condition type.

1.2.1 Go to /IRM/IPSPRO
1.2.2 Create a new condition table by selecting IPSPRO > Incentive and Payback Module
> Basic Functions > Pricing Sales > Pricing Control  Define Access Sequences
1.2.3 Maintain Access Sequence VALL for the Table created in the above steps 1.1.3 and
1.1.4

Section 1.3 – Maintain Condition Types

Price elements are represented in the system by condition types. Price elements can be, for
example, prices, surcharges, discounts, taxes, or freight, and are stored in the system in
condition records.

1.3.1 Create a new condition table by selecting /IRMIPSPRO > Incentive and Payback
Module > Basic Functions > Pricing Sales > Pricing Control  Define Condition Types
1.3.2 Maintain Condition Type VIE1 with the following information:

VIE1
Condition Type
Description Eligible Customer
Access Sequence VALL
Condition Class H Determining sales deal
Calculation Type G Formula
Condition Category X Customer reserve X
Manual Entries D Not possible to process manually
Item Condition Enable

June 2023 Page 3 of 11

 Use/Test Case #BB

Proposed Valid-From 3 First day of year

Proposed Valid-To 2 End of the current year
Delete From DB A With Popup

1.3.3 Maintain Condition Type VIE2 with the following information:

VIE2
Condition Type
Description Eligible Material
Access Sequence VALL
Condition Class H Determining sales deal
Calculation Type G Formula
Manual Entries D Not possible to process manually
Item Condition Enable
Proposed Valid-From 3 First day of year
Proposed Valid-To 2 End of the current year
Delete From DB A With Popup

1.3.4 Maintain Condition Type VIML with the following information:

VIML
Condition Type
Description Material List
Access Sequence VALL
Condition Class H Determining sales deal
Calculation Type G Formula
Manual Entries D Not possible to process manually
Item Condition Enable
Proposed Valid-From 3 First day of year
Proposed Valid-To 2 End of the current year
Delete From DB A With Popup

Section 1.4 – Define Price Sheets

Price Sheets are used to save the data of the price records that are created in different
applications.

1.4.1 Go to the transaction /IRM/GPRSPRO.

1.4.2 Create a new price sheet by selecting /IRM/GPRSPRO > Data Maintenance –
Pricing > General Maintenance > Price Sheets > Define Price Sheets.
1.4.3 Maintain the Price sheet for Condition type VIE1 with the following Information:
Application V Sales/Distribution
Condition Type VIE1

June 2023 Page 4 of 11

 Use/Test Case #BB

Condition Table 966

Alias Eligible Customer
1.4.4 Maintain the Price sheet for Condition type VIE2 with the following Information:
Application V Sales/Distribution
Condition Type VIE2
Condition Table 967
Alias Eligible Material
1.4.5 Maintain the Price sheet for Condition type VIML with the following Information:
Application V Sales/Distribution
Condition Type VIML
Condition Table 967
Alias Material List

Section 1.5 – Maintain Condition Type Group

In this Customizing activity, the user will define condition type groups for sales conditions.

1.5.1 Go to SPRO
1.5.2 Create a new Condition Type Group by selecting Logistic General > Settlement
Management > Condition Contract Management > Condition Contract Conditions >
Sales > Define Condition Type Group
1.5.3 Maintain Condition Type Group with the Condition Type Group VICH and Description
Schedules Group.

Section 1.6 – Assign Condition Type to Condition Type Group

In this Customizing activity, the user will assign sales condition types to a condition type
group.

1.6.1 Create a new Condition Type Group by selecting SPRO > Logistic General >
Settlement Management > Condition Contract Management > Condition Contract
Conditions > Sales > Assign Condition Type to Condition Type Group
1.6.2 Enter the Condition Type Group created in step 3.4.3 and select Usage as C No
Limitations Concerning Condition Contract Number.
1.6.3 Assign Condition Type to the Condition Group created in the above steps.

Condition Table
Condition Type
VIE1 966
VIE2 967

VIML 967

Section 1.7 – Maintain Number Ranges for Condition Contracts

When the user creates a condition contract, the system assigns a unique number to identify the
contract. This number is derived from the number range defined for the contract type.

1.7.1 Create a new Condition Type Group by selecting SPRO > Logistic General >
Settlement Management > Condition Contract Management > Condition Contract
Maintenance > Define Number Range for condition contracts.

No From No. To Number

01 000000001 1999999999

June 2023 Page 5 of 11

 Use/Test Case #BB

Section 1.8 – Create Condition Contract Type

In this Customizing activity, the user will define Condition Contract Types for different
condition contract processing purposes. The condition contract type determines the behavior
and layout of a condition contract maintained.

1.8.1 Go to SPRO
1.8.2 Create a new Condition Contract Type by selecting Logistic General > Settlement
Management > Condition Contract Management > Condition Contract Maintenance
> Define Condition Contract Type
1.8.3 Maintain Condition Contract Type with the following fields:

VISO
Condition Contract Type
Description Agrm Schedules - On Demand
Number Range 01
Type of Contract Partner N No Contract Partner
Type of Eligible Partner N No Eligible Partner
Condition Contract Category 0B Billbacks
Sales Condition Type Group VICH
Change Via UI N No Change via User Interface

Section 1.9 – Define Number Ranges for Agreement

1.9.1 Go to the transaction /IRM/IPSPRO.
1.9.2 Maintain number ranges for agreement in the below configuration path: /IRM/IPSPRO
> Incentive and Playback Module > Global Settings > Define Number Ranges for
Agreement (Version 2).
No From No. To Number
01 000000001 1999999999

Section 1.10 – Create Agreement Type

The Agreement Type determines which rules or conditions will be available for the Agreement,
including default data such as validity dates, partners, and tabs.

1.10.1 Enter the IMG menu or enter /IRM/IPSPRO in the Command field.
1.10.2 Create the agreement type by selecting Basic Functions  Pricing - Sales 
Pricing Agreements > Maintain IP Agreement Types – Sales
1.10.3 Double-click on the Maintain Agreement Types for Billbacks / 1 option.
1.10.4 Enter the following data to create a new Agreement type:
VISO
Agreement type
Description Marketing Funds
Contract Type VISO
No. Range no. 01

1.10.5 Click on the Save button.

Similarly, Create another Agreement type, “VITM”. Follow the same steps as above for creation.

June 2023 Page 6 of 11

 Use/Test Case #BB

Configuration Step 2: Configure File Template

After this exercise, the user will be able to:

 Configure a File Template

Section 2.1 – Create a File Template

In the file template, sections and mappings are maintained that can be used in upload
functionality.

2.1.1 Go to /IRM/IPAGFTPM
2.1.2 In Change mode, click on create icon.
2.1.3 Enter File Template as VIAGR, Description as PQ Use Case – DND, File format- CSV,
Application – 0 Billbacks.
2.1.4 In the Attribute section, maintain Agreement Type as VISO. Hit Enter.
2.1.5 Now click on the Section tab. For the HD Header section, maintain the Indicator as
$HDR.
2.1.6 Mark the Display title checkbox, and give the position as 1. Hit Enter.
2.1.7 Now click on the Mapping tab, enter the following data, and Hit Enter.

Section Field Name Position Value Field Mask

HD Header BOART_AG 1
HD Header KNUMA_AG 2
HD Header BOTEXT 3
HD Header ABREX 4
HD Header VKORG 5 0001
HD Header VTWEG 6 01
HD Header SPART 7 01
HD Header DATAB 8 DD.MM.YYYY
HD Header DATBI 9 DD.MM.YYYY
HD Header WAERS 10

2.1.8 Click the Parameters tab, maintain the following data, and Hit Enter.

Parameter Description Position Value

BOART_AG Agreement type 1 VITM

2.1.9 Save the File template.

2.1.10 Click continue in the log display.

June 2023 Page 7 of 11

 Use/Test Case #BB

Configuration Step 3: Configure File Template Variant

After this exercise, the user will be able to:

 Create a Number range for the file template variant.

 Create a File Template Variant.

Section 3.1 – Create Number Range and Create a File Template

Variant
In this step, the user will create a number range for the file template variant. A file template
variant can be used in the file submission workbench.

3.1.1 Go to /IRM/IPSPRO > Incentive and Payback Module > Global Settings > Define
Number Ranges for File Template Variants
3.1.2 Click “Change Intervals” to enter the following data and Hit Enter.

Number Range No. From No. To Number

01 00000000000001 00000001000000

3.1.3 Click Save. Click continue in the log display.

3.1.4 Go to /VTA/BFTPVM.
3.1.5 In the change mode, click on the ‘Create’ icon.
3.1.6 Enter the file template as VIAGR, Description as PQ Use Case – DND.
3.1.7 Hit Enter.
3.1.8 Now go to the ‘Parameters’ tab, change the BOART_AG value to VISO, and enter the
following data.
Field Name Value
VKORG 0001
VTWEG 01
SPART 01

3.1.9 Save the Variant. Note the Variant created.

June 2023 Page 8 of 11

 Use/Test Case #BB

Configuration Step 4: Configure Submission Type

After this exercise, the user will be able to:

 Configure a Submission Type

Section 4.1 – Create a Submission Type

4.1.1 Go to /IRM/IPSPRO > Incentive and Payback Module > Basic Functions > Define File
Submission Types > Define File Submission Types.
4.1.2 Click on New Entries
4.1.3 Enter Submission Type as VIAG, Object Type as AG, Application as V, Description as
PQ Use Case – DND, Directory – Use local system directory (Ex: /usr/sap/T4H/D00/work),
and file template as VIAGR.
4.1.4 Save the Submission type.

Exercise Step 1: Parameters in File Template

June 2023 Page 9 of 11

 Use/Test Case #BB

After this exercise, the user will be able to:

 Create a File Submission and change the parameters dynamically.
 Upload a file using file submission and create an agreement.

Step 1.1 – Create a File Submission

1.1.1. Go to /VTA/BFSM
1.1.2. In change mode, click on Import File (F5) button.
1.1.3. Enter the Submission Type as VIAG, Processing Type as O Online
1.1.4. Now go to the Parameters tab. Here the parameter is fetched from the file template.
1.1.5. The user can change the value dynamically in the parameter tab.
1.1.6. Change the Agreement type from VITM to VISO. Hit Enter.
1.1.7. Now go to the File tab. Enter the File Reference as PQ_Parameters and Select the File
Path from F4 Help (Select the file PQ_Parameters from Desktop). Hit Enter.
1.1.8. Click on Upload.
1.1.9. Click ’Allow’ if a pop-up raises.
1.1.10. A message ’ File reference xx has been saved’ is displayed. Click Continue in the pop-
up.

Step 1.2 – Upload Agreement using File Submission

1.2.1 Go to /IRM/IPBBAGUPLD
1.2.2 Enter the File source as File Submission and Submission Type as VIAG.
1.2.3 Get the Processing Options from the File Submission. File Name – The file
path from submission, File Reference as PQ_Parameters, Submission Date – Today’s
Date, File Status as A. Hit enter.
1.2.4 Click on Execute. The agreement should be created.
1.2.5 Note the agreement number and click on continue.
1.2.6 Now go to /IRM/IPBBASP transaction.
1.2.7 Click on the search icon and search for the agreement created in step 1.2.5.
1.2.8 Verify that the agreement is created with the VISO agreement type.

Exercise Step 2: Variants in File Template

June 2023 Page 10 of 11

 Use/Test Case #BB

After this exercise, you will be able to:

 Create a File Submission with variants.
 Upload a file using file submission and create an agreement.

Step 2.1 – Get the Variant

2.1.1 Go to /VTA/BFTPVM
2.1.2 Click on the Search icon and enter the variant created in configuration step 3.1.9. (or)
Enter File Template as VIAGR and Hit Enter.
2.1.3 Click on Execute.
2.1.4 Verify the Variant and the Parameters.

Step 2.2 – Create File Submission with Variant

2.2.1 Go to /VTA/BFSM
2.2.2 In change mode, click on Import file (F5).
2.2.3 Enter the Submission type as VIAG, Processing Type as O Online
2.2.4 Select the variant from the dropdown from step 2.1.4.
2.2.5 Go to the Parameters tab and verify that the values from the variant parameters tab
have defaulted into the submission.
2.2.6 Now go to the File tab. Enter the File Reference as PQ_Variant and Select the File
Path from F4 Help (Select the file PQ_Variant from Desktop). Hit Enter.
2.2.7 Click on Upload.
2.2.8 Click ‘Allow‘ if the pop-up raises.
2.2.9 A message ‘File reference xxx has been saved‘ is displayed. Click continue in the pop-
up.

Step 2.3 – Upload Agreement using File Submission

2.3.1 Go to /IRM/IPBBAGUPLD
2.3.2 Enter the File source as File Submission and Submission Type as VIAG.
2.3.3 Get the Processing Options from the File Submission. File Name – The file path from
submission, File Reference as PQ_Variant, Submission Date – Today’s Date, File Status as A.
2.3.4 Hit Enter.
2.3.5 Click on Execute. The agreement should be created.
2.3.6 Note the agreement number and click Continue in the pop-up.
2.3.7 Now go to /IRM/IPBBASP transaction.
2.3.8 Click on the search icon and search for the agreement created in step 2.3.6.
The agreement should be created with the data given in the parameters tab.

June 2023 Page 11 of 11