Setting up Mass Processing Jobs in APO3.

0
Index:
Section Page

Setting up Mass processing job to generate Characteristics Combinations 2

- Detailed Steps 2
- Transaction /SAPAPO/MC62 3
- Save as variant 5
- Setting the date range in the variant 8

Setting up Mass processing job to generate proportional Factors 9

- Detailed Steps 9

Mass deletion of Characteristic Combinations 11

- Mass Deletion not available
- Mass processing job example

Mass processing for the deletion of products and locations 14

Deletion of Versions and Version data 15

Deletion of LiveCache Order data 16

Sending Mail 17

Transfer of Master Data from R/3 to APO (periodic) 18

Reprocess the events in outbound event channel 19

Transfer changes to PPMs from R/3 to APO 20

Transferring Global Setting from R/3 to APO 22

1
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
Generate Characteristic Combinations in batch:

The report that generates the characteristic combinations is:

/SAPAPO/TS_PLOBS_GENERATE.

There are two very simple ways to set up this particular job:
- Using TA SE38, creating a variant and then creating a mass processing job
- Using TA /SAPAPO/MC62, selecting to create characteristic combinations
and executing the job in the background. This is probably the fastest (and
easiest) way to do this.
- Enter your planning object name and select to generate characteristics.
- You will get a second screen that will prompt you for additional
information.
- Enter the information and select to save as a variant (for now don’t worry
about the from and to dates)
- You will be prompted to enter a name and description for the variant.
- Now you want to define the start and end dates as dynamically calculated
(or a fixed range, reading values from an input variable). Check the
boxes under the ‘Selection Variable’ column (field name ‘L’).
- From this screen select the ‘Selection Variables’ button on the status bar.
- The selection variables default to entries from the TVARV table. For this
example, I am assuming that the variant will dynamically calculate the
start and end dates based on the current date. Double click on the ‘D’
column for the selection criteria.
- Then select from the drop down and choose a dynamic date calculation.
These are system-supplied variables; you only need to select how many
days (calendar or working) you want to subtract from the current date to
get the start date and how many days to add to the current date to get the
end date.
- Save the variant and give it a name.
- Choose to execute the program in the background. Path:
Program!Execute in Background. Follow the prompts and run the job.
- Use TA SM37, find the job - ‘/SAPAPO/TS_PLOBS_GENERATE’.
- Select this job and copy. Path: Job!Copy. Give it a name that you will
use in production.
- Use TA SM37, (be sure that you have job status ‘Scheduled” selected) and
find the job you just created. Select that job and change the job. Path:
Job!Change.
- From the “Change Job” screen, select ‘Step’.
- Select the single step and take the option to change (Pencil).
- Under the ABAP Program section of the screen, select the variant you
created previously. Save. Back out of the transaction and save whenever
prompted.

2
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
Path: Master Data!Demand Planning Master data!Maintain Characteristic Values
Transaction Code: /SAPAPO/MC62

Once you are here, enter your planning object name and select the second option under
the “Maintenance of Characteristic Combinations”. This will automatically generate all
possible characteristic combinations based on the existing data within the InfoCube.

<<Do not worry about saving the variant here >>

Once you have entered your information, select to “Execute”.

3
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
This is the second portion of the “Generate Characteristics” process. The Planning
Object Structure entered in the first screen is passed to this report (it is protected in this
screen).

Her you only need to enter the InfoCube, Version and select to create Time Series
Objects. Accept the defaults for the dates. They will be changed later in the process.

Now take the option to save. This will bring you to the next screen.

4
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
This is where you will name the variant and give it a brief description.
(BRAUN and ZCEW_BR_VA).

This is where you will set the start and end dates for the selection range. You need to
identify which fields in the variant will be populated from selection variables.

Select the fields as showed above.

Then select the ‘Selection Variables’ button from the status bar.

You will get the next screen.

5
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
For the characteristic combinations, you will need to adjust the date range in the

selection. The default is for the values to be supplied from the TVARV table. (The
green light Icon under the ‘T’ column)

Double click on the ‘D’ and you will be able to use the system date, SAP supplied
variables and your own criteria to dynamically generate the start and end dates.

6
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
 7
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
You will get this next screen, when you select the drop-down box. For this variant, I
think the Current date + / - (either working days or calendar days) is the best ‘fit’.
Since this is the start date, select two years prior:

Do the same thing for the end date of the propagation range (end date)

If you need a specific ‘frozen’ date as the end of the horizon, create a variable in the
TVARV table and supply the appriopiate date.

8
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
Calculate proportional factors:

The report that generates the proportional factors is:

/ SAPAPO/RMDP_SHARE_MANAGER

There is only one very simple way to set up this particular job:
- Using TA /SAPAPO/MC8V, selecting to Calculate proportional factors and
executing the job in the background. This is the fastest (and only way) to do
this.
- Enter your Planning Area Name and InfoCube. Select the execute button.
- You will get a second screen that will prompt you for additional
information.
- Enter the information and select to save as a variant (for now don’t worry
about the from and to dates)
- You will be prompted to enter a name and description for the variant.
- Now you want to define the start and end dates as dynamically calculated
(or a fixed range, reading values from an input variable). Check the
boxes under the ‘Selection Variable’ column (field name ‘L’).
- From this screen select the ‘Selection Variables’ button on the status bar.
- The selection variables default to entries from the TVARV table. For this
example, I am assuming that the variant will dynamically calculate the
start and end dates based on the current date. Double click on the ‘D’
column for the selection criteria.
- Then select from the drop down and choose a dynamic date calculation.
These are system-supplied variables; you only need to select how many
days (calendar or working) you want to subtract from the current date to
get the start date and how many days to add to the current date to get the
end date.
- Save the variant and give it a name.
- Choose to execute the program in the background. Path:
Program!Execute in Background. Follow the prompts and run the job.
- Use TA SM37, find the job - ‘/SAPAPO/RMDP_SHARE_MANAGER’.
- Select this job and copy. Path: Job!Copy. Give it a name that you will
use in production.
- Use TA SM37, (be sure that you have job status ‘Scheduled” selected) and
find the job you just created. Select that job and change the job. Path:
Job!Change.
- From the “Change Job” screen, select ‘Step’.
- Select the single step and take the option to change (Pencil).
- Under the ABAP Program section of the screen, select the variant you
created previously. Save. Back out of the transaction and save whenever
prompted.

9
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
All fields listed above are mandatory. These values are passed to
/SAPAPO/RMDP_SHARE_MANAGER when you execute the report.

10
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
Save these values in the variant.

You can also use the dynamic date selection that was outlined in the previous example.
In this report, you may have two sets of dates to define.

11
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
Delete Characteristic Combinations in batch:

This is not available since the selection screen that is used for deletion is a dynamically
generated. If you need this functionality, you will need to have an ABAP report (suggest
that you use the generated ABAP from the online transaction)

An example of Mass processing jobs to generate proportional factors in batch is:

12
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
If you have not saved a generated program previously, these are the basic steps:
<<Make sure the ID you are using has access to SE38 and has either SAP_ALL or
Developer authority>>
- Take the option to Delete Characteristic Combinations.
- (TA - /SAPAPO/MC62)
- Select Program!Execute in the Background
- Select the start date and time of the mass processing job to in the future
- Save
- Use SM37 and select the job you have just created.
- From the top down-down menu, select Go To! Program
- This will put you in SE38 with the generated report as the source code
- Take the option to copy. Copy the report to Z-Program and save it.
<<You should have the option during the copy to copy the variants
associated with the report. Take this option>>
- When prompted for a development class, take the option for ‘Local
Object’. This can be changed later.

13
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
Processing the Deletion of Products and Locations:

To delete products flagged for deletion:

Path: Master Data! Product ! Extras ! Delete Products
(Transaction - /SAPAPO/MAT1)
<< You set the deletion flag using the path:
Master Data ! Product ! Product ! Mark for Deletion >>

This will create a mass-processing job to process the deletion in the background. There
are no variants to create.

The ABAP code that processes the deletion is /SAPAPO/DELETE_PRODUCTS. This

can be set up in a mass-processing job directly from SM36.

To delete locations flagged for deletion:

Path: Master Data ! Location ! Location !Extras !Delete Locations
(Transaction - /SAPAPO/LOC3)
<<You set the deletion flag using the path:
Master Data ! Location ! Location ! Location !Deletion Flag >>
This creates a mass-processing job that processes the deletion of locations in the
background. There are no variants.

The ABAP code that processes the deletion is /SAPAPO/DELETE_LOCATIONS. This

can be set up in a mass-processing job directly from SM36.

14
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
Deletion of a version (except ‘000’ which cannot be deleted)
The ABAP report that processes the deletion is /SAPAPO/VERSION_DELETE.
The variant for this ABAP can be created in SE38 and requires only the version to be
deleted and a selection specifying if the entire version or only the transactional data is to
be deleted.

You cane set this up using SE38:

Create the variant specifying the version to be deleted and select the radio button
to select only transactional information or if the entire version is to be deleted.

15
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
Deletion of LiveCache Order Data:

The ABAP report that processes the deletion of data from LiveCache is
/SAPAPO/RLCDELETE.

Select the application where you want to delete data from (SNP or PP/DS)
Select the radio button to either delete only from APO or from APO and the
corresponding data from R/3.

16
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
Sending Mail via a batch process:
<<Use this to email alerts>>

ABAP Report: RSCONN01. The report has two input fields:

MODE: This is the mode of transmission of the email
OUTPUT: This checkbox lets you select to have a log generated of all the objects
selected for transmission.

The list of valid input fields for MODE is:

FAX – Fax transmission
INT – Internat email
PAG - Pager
PRT – Print file
RML - RML Orders
TEL - Telephone
X40 – X400 protocol
* - All of the above

The values for the ‘Output’ box are:

Blank – No Log generated
X – Log will be generated

17
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
<<This runs only on the R/3 side of the APO landscape>>
Transfer Master Data Changes from R/3 to APO on a periodic basis:
- Doing this periodically reduces the amount of traffic on the communications
channel. There are selection options for several object types, depending on
the volume of transactions and change you maybe able to live with one or up
to eight jobs to send the data to APO. You do not need to create additional
integration models for this.

The ABAP report that processes the send of new data is RCPTRAN4. This same report
process all eight categories listed above.
To create a mass processing job:
- Create a variant from this screen, identifying the logical system
(TAPCLNT100) and the object types that you want to be processed (in this
case, only material masters is checked).
- Save the variant (Save Icon).
- Use SM36 to create a mass-processing job, list ‘RCPTRAN4’ as the ABAP
report and select the variant you created from the drop down box.
- I would suggest that you schedule this to be time periodic and run it once a
day during the late evening before the night processing.

18
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
Re-process the events in the outbound event channel:

Use this transaction/job to clean up entries that are in the outbound qRFC channel. There
can be a number of reasons why entries can be in the channel with an error:
- Sales Order for a Product that has not been extended to the customer location
in APO. Correct the problem, by extending the product in APO.
- System overload in either APO or R/3. This is temporary. No action needed.
- Unit of measure not defined in APO for the product. Update the UOM’s from
the Administrator Workbench.
- This is only an example. The process here is to use the errors in the event
channel to identify problems and then correct then in APO. The periodic
reprocessing will clear the channel and problems are corrected.

The ABAP report that reprocesses the events is RSARFCEX. Below are sample entries
for the variant:

For the date range, the selection here was to go back 30 days.

19
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
Transfer changes to Production process models to APO:

The ABAP report that processes the changes to PPMs is RSPPMCHG.

Like the Master Data changes for the material master, vendors, customers, etc. this
process should be run once daily. I would suggest that it be run after the master data
transfer or made the second step in a mass processing job that processes the daily transfer
of changes from R/3 into APO.

20
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
Transferring Global Settings between R/3 and APO

You will need to transfer Global setting between R/3 and APO (if the APO
system is connected to one or more R/3 systems). Examples of these “Global Settings”
are:
Unit of Measure definitions – i.e. FT3, M3, CM, H, YR etc.
Currency definitions – i.e. USD, Yen, Euro etc.
Fiscal Variants
Factory Calendars
Exchange rates (17 flavors – not quite Baskin-Robbins)

Initially when the APO system is setup and configured these will be transferred
after the Source R/3 system is defined in the Source System tab of the Administrator
Workbench. It is very easy to overlook this since most data transfer is done through the
CIF and these data elements can not be defined in any integration model.

When you transfer these settings, you only have the ability to restrict by type
(UOM, Currency etc) you do not have the ability to select on volumetric units and
transfer them or selecting only SAP delivered calendars to be transferred. Once you
select the category, it’s all or nothing.

To set-up the process unattended transfer, there are several things that must be
done first:
- Create an entry in the TVARV table for the Logical system name you will be
connecting with during the transfer process.
- Identify which data elements are to be transferred and on what schedule
(daily, weekly, monthly or on demand).
- If the APO system is connected to multiple R/3 systems, determine what data
is coming from where (fiscal variants and factory calendars that do not have
unique names will be overwritten; last system to transfer will overwrite
whatever is in APO). For UOM’s and Currency definitions the transfers will
be cumulative; you will have a definition in APO if they exist in any of the
R/3 systems you are connected to. For exchange rates, you should transfer
them from a single R/3 system (preferably the system that is used for financial
reporting).

For simplicity, I will assume a single R/3 connection and a separate job for each
data type. The report that runs this unattended transfer is ‘RSIMPCUST’. We
will need one entry in the TVARV table and a separate variant for each data type.

21
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
 Creating a TVARV entry:

The TVARV table holds the selection variables that are used in variants. The
easiest way to create an entry in this table is by editing the table directly, using
standard SAP utilities. The transaction code for this is SE11 or the path is:

SAPMenu !Tools ABAP/4 Workbench!Development!ABAP Dictionary.

Enter ‘TVARV’ in the Database Table field of the SE11 screen. Take the option
to ‘Display’. We will be creating an entry in the table (not changing the table
definition) so change or create are not suitable choices.

On the next screen you will see the table definition for TVARV, from the top of
the screen take the option to create entries in the TVARV table. The path to this
is:
Utilities!Table Contents!Create Entries

22
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
 You will get a screen like this:

These are the minimum fields needed for this entry:

VARIABLE NAME: The name of the variable is ‘LOGICAL_SYSTEM’ (you
can customize this. This will be the name of the selection variable that will be
defined in the variant for the report RSIMPCUST)
SELECTION CATEGORY: Set this to ‘P’.
NUMBER: The system will default a value for this field.
INCL/EXCL: This is an include or exclude option. Select ‘I’ for include
OPTION: Select ‘EQ’ for equal
SELECTION VALUE (LOW): This is the technical name of the R/3 system as
it is defined in the SM59 connection. In this example RCDLOG210 is client 210
in system RCD.
SELECTION VALUE (HIGH): Leave this blank.

23
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
 Creating the variant for RSIMPCUST:

Create the variant using SE38. The ABAP report name is RSIMPCUST, select
the radio button for variant and take the ‘Change’ option. On this second screen,
type in the Variant Name (here it is TRANS_FISCAL) and take the create option.

In the next screen, you will have selection options and a Button on the Tool Bar
marked ‘Variant Attributes’. Select this and you will get a screen like the one
above.

The Variant Name is carried over and you will need to enter a description. You
also need to identify that the Logical System name will be passed into the variant
by a selection variable. You do this by selecting (with a check mark under the ‘L’
column) the LOGSYS entry field. After you have done this, select the ‘Selection
Variables’ button from the Tool bar and get a screen like the one on the next page:

24
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
 Here, you assign the TVARV entry to the field marked in the previous screen.
All variables in the TVARV table are available through the drop-down option
here.
Take the option to ‘SAVE’ and return to the previous screen. Save again and you
are back at the initial screen for the report.

In this screen, you select which data types are to be transferred to APO and
whether the updates will replace or be incremental to the data that is already in
APO. (In some cases – mentioned previously, this is no choice).

25
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
 26
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
 There are two ways of transferring exchange rates into APO:
- Connecting to R/3 and transfer a selected exchange category into APO. This
process uses report RSIMPCURR.
- Uploading data from a flat file into APO. The file can exist either on the
client workstation or on a network drive. This process uses the report
RSIMPCURFILE (Flat file).

Both of these features can be scheduled as background mass processing jobs. If you are
connecting to an R/3 system you will need to use the Selection Variable for the Logical
System.

This example is set for one type of exchange rate (‘M’). The source system values are
automatically populated from the Selection Variable. All other rules for saving the
variants and creating the mass processing job apply here. (These steps have been
explained earlier in the document).

27
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM
If you are importing exchange rates from a flat file (either on your desktop or from a
network drive), use the ABAP report RSIMPCURFILE.

For the flat file there is no Selection Variable needed. You will need to specify the full
path of the file regardless of where it is located. You can only schedule a background
process (mass processing job) if the file is on an application server.

28
SAP Internal Only - Do Not Distribute
11/28/01 5:56 PM