This document provides steps required to load data in SAP using one of the SAP interfaces. This document will be use at the time of proof of concept to demonstrate ability of Business Objects Data Services (BODS) to invoke RFC enabled BDC to load data in SAP.
The main objectives are:
This document provides systematic approach for the data load in three sections:
Each of above sections provide information as in how to configure the specific parameters required to get both SAP & BODS ready to communicate with each other. Screen shots provided for better understanding of the parameters & their configuration.
Following is the required configuration on SAP side.
ZFSP0 is a structure containing fields for creating GL Accounts in transaction FSP0.
The ZFSP0 Structure fields are as follows.
1. ZFSPO Structure
2. ZFSPO_Message Structure
Use T-CODE SHDB to visit FSP0 and do recording according to requirements
3. Transaction Recording
4. Transaction Recording Continue
Attributes information Tab for Input / Output Parameters is as follows
Function Builder
5. Function Module
The RFC enabled BDC is getting ZFSP0 as input, which is in structure format, it defines BAPIRET2 as RETURN Table for Messages.
Function Builder
6 BDC Parameter Information
7 BDC Source Code
8. BDC Source Code continue
9. BDC Source Code continue
Following is the required configuration on BODS side.
To simulate legacy data process in BODS we are creating input data file. This file is a text file with required fields only, to be loaded in SAP. Since this is a proof of concept, we are not demonstrating any transformation capabilities of BODS but just the ability to invoke SAP interfaces to load data in SAP.
KTOPL | SAKNR | KTOKS | XPLACCT | TXT20 | TXT50 |
CAAU | 194311 | BS | Testing | Testing for BODS | |
CAAU | 194312 | BS | Testing | Testing for BODS | |
CAAU | 194313 | BS | Testing | Testing for BODS | |
CAAU | 194314 | BS | Testing | Testing for BODS | |
CAAU | 194315 | BS | Testing | Testing for BODS | |
CAAU | 194316 | Testing | Testing for BODS | ||
CAAU | 194317 | BS | Testing | Testing for BODS | |
CAAU | 194318 | BS | X | Testing | Testing for BODS |
CAAU | 194319 | BS | X | Testing | Testing for BODS |
CAAU | 194320 | BS | Testing | Testing for BODS |
Create new flat file source (formats tab) in BODS. This is the way BODS links any external files so that they can be use as source on Data Flow. Create source & link to the Input Data File created in above section.
10. Flat File Source INPUT_GL_DATA
Steps to create job is as follows:
BODS JOB
11. BODS Designer Data Flow View
BODS Job is using Query transformation three times in succession.
NRDM - A query transform is used to pass complete schema. Here in this transformation required struture is created that will be required as input to the RFC enabled BDC.
12 NRDM Query Mapping
BDC_Call - A query transform to call BDC (Already imported in SAP Datastore)
To avoid Calling BDC for each record, we are restricting function call to execute only once by using where clause. Since RFC enabled BAPI accepts table as input, it takes all records present and insert into SAP
13. BDC_Call Query Mapping
14. Input Parameter to BDC
Query_Unnest - A query transform to unnest “RETURN” schema with AL_RFC_RETCODE
Output table is mapped to accept ‘GT_MSG’; "return table for messages" to check the status per record.
15. Query Unnest
Verify the BODS Job by clicking on the Verify button to check on errors if any.
Execute verified Job by right clicking on the Job and click on execute (option)
Right click on the job to execute & select Execute from options.
16. Running Job
Execution Properties
Keep default options on this screen & click on ok to execute
17. Properties
Go to the Log tab, expand the Job, and click on the execution log to check the entries.
18. Log View
Click on the second button from left on the Log view screenshot to check processed data statistics.
19 Statistic View
After successful execution go back to Data Flow to check the data returned by RFC-BDC.
Confirm that the returned data inserted in table (emp_data_rfc_ouput)
20 Returned Data View
Connect to SAP using SAP GUI
Use T-CODE SE11 and check entries in table SKA1 (G/L Account Master (Chart of Accounts)) to confirm the data insertion.
21 SAP Load Confirmation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
5 | |
5 | |
4 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 |