This article covers the steps to follow to automate the Data Manager packages in BPC NW 7.5. Though BPC Data Manager packages can be configured and scheduled at a given time with in BPC for Excel, however we also have the ability to automate the package and incorporate the same into a custom process chain for end to end automation of data loads from ECC to BW to BPC. Perhaps by using this technique we also can debug a package in case if the log generated by running the package isn’t helpful to identify an issue.
II Automation of a package can be segregated into two sections:
Answer Prompt file.
II.1 what is an Answer prompt file?
In general, it is mandate to supply all the all the required prompts to execute a package successfully. Therefore any attempt to automate the execution of package involves supplying the answers to these prompts through some means. These answers when bundled into a file can be called as an Answer Prompt file.
II.2 what is a program Variant?
Using the program UJD_TEST_PACKAGE a data manager package can automated.This program requires certain parameters to be entered like Appset, Application Id, User, package, Answer Prompt file etc. Once all the parameters are supplied the program can be saved as a variant for further usage in process chains using ABAP Process type.
III. Answer Prompt file creation:
Step 1- Execute Data Management Package:
Logon to Office Client chose your respective Appset and Application.
Run the Data Management Package with all the necessary required parameters.
Trace the log file of the success package and make necessary modifications to make it ready for automation.
Step 2- File service in BW:
Log on to BW system, enter t-code UJFS
Follow the steps defined below to identify the log file.
Enter Appset name and click Execute
Step 3- Package Log:
All the logs are stored on private publications folder expand it to identify the user id using which the package has been executed. The answer prompt files are stored in the folder called temp files.
Sequence: Root > Appset > Application > Private Publications > Domain > User id > TempFiles
Typical list of log files can be seen as below:
The logs generated by running the packages by a specific user can be seen under that user id.
Step 4- Identify specific log file:
The log files you see here are a mix of all data management package logs executed. Easiest way to identify the log file is each log is generated with the executed package name followed by date and time combination.
Step 4.1 Sample Master data Log file:
Highlighted section the package name and date and time the package was executed.
Here the package name is “Import bw masterdata”.
Step 4.2 Sample Master Data hierarchy load log file:
Step 4.3 Sample Transaction Data load log file:
Similar is the case with Master data hierarchy load and transaction data load from BW to BPC.
Highlighted section denotes Data Management Package name followed by date and time stamp.
Tip: you can identify latest executed data management package log from the bottom of the log files list.
Step 5- Download log file:
Once the log file is identified, it has to be downloaded to a desirable location and modify it in required format.
Right-click on the chosen file and click on Download Document option from the menu.
From the prompt screen click Yes.
Specify the file location where you intend to save and click Save.
Step 6- Trimming pertinent portion of Answer prompt file:
Downloaded Log may look something like below.
From the log remove the unwanted portion (section highlighted in Red).
View of the section required from the above log file.
Trim the file with few replacements as described below to make it fully qualified as an Answer prompt file.
Replace “<” with “<” and “>” with “>”
Tip: You can use simple ‘find’ and ‘replace’ option in the notepad to perform this task.
Save this notepad with a name in a designated location to be recalled in UJD_TEST_PACKAGE program in BW
III. Variant Creation:
Automating the DM packages using package log generated in BW file service.
Logon to BW system, go to SE38, enter the program name UJD_TEST_PACKAGE and click Execute.
Tip: As a best practice save this program and rename with Z to save your selves from unwanted/unexpected changes to this SAP Program during future upgrades.
Next screen enter all the required parameters in the selections.
User ID: Enter the user Id
Tip: as a best practice configure the user id with BPC system id (eg: BPC_SYSADMIN) instead of developer id. Package execution may fail if the developer id assigned is removed from the user list in BPC Admin.
Package ID: Enter the package ID for which the automation is being setup.
Appset ID: Enter Appset
Appl ID: Enter the Application Name
Team ID: Can be left blank
Answer Prompt: An answer prompt file has all the prompt selections entered while executing a package. All those variables are bundled into a file (typically a notepad), is called into this selection using F4.
Schedule info (XML): Default
Once all the required values are maintained click on Execute
Next screen give the Variant name and Description and click Save .
This variant can be used in the process chain to automate the data management package.
It is evident from the above that automation of Data manager packages in BPC NW 7.5 is simple. Few steps and tips will help you achieve desired end result.