Ansicht
Dokumentation

RNCTTBAPIGMAPTAB - IS-H BAPI Generating Program for MAPTABFLD-FORM for BAPIs

PERFORM Short Reference   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Description

This program is a special utility for creating IS-H BAPIs. It may only be used for this purpose, and is based on very specific conditions (see below). The program may only be used by software developers who have a thorough understanding of this area!

The mapping of structure names and field names from internal structures to the corresponding external structures constitutes a problem. The global, internal table GL_MAPTAB is filled and evaluated for this in the IS-H System. This table is filled in special FORM routines, one for each structure. These are the routines that are generated by this program.

The program generates the FORM routine called ADMAPT_bapistructurename (bapistructurename = name of parameter of a structure in the BAPI interface) in the target include program of the IS-H BAPI function group. This FORM is simply appended to the existing source code. Caution: when the same FORM routine occurs more than once the generated program contains errors. Nothing is overwritten. Problem locations are identified by '???'. These must be corrected subsequently. When such corrections are made, the name of the person making the manual correction, the date/time of the correction and what the correction involved should always be added to the FORM header.

The FORM routine for non-structure parameters (ADMAPT_PARAMETERS) must be created and maintained manually. This program can be of no assistance here. A template is provided in the function group 2099.

Requirements

1. A MAP2* module must exist in the function group. You must enter the corresponding program name (e.g. L2099U03) on the selection screen. Here it is irrelevant whether the module is a MAP2E* or MAP2I* module. Since, however, FORMs are usually only important for import parameters, these are almost always MAP2I* modules. On the other hand, a corresponding FORM ADMAPT_bapistructurename would have to exist for each MAP2I* module, to ensure errors are correctly reported.
2. The (include) program, in which the FORM should be generated must have already been created.
3. There is only one corresponding internal structure for each external BAPI structure. If this is not the case, a second FORM must be generated and renamed.
4. Exactly one API is called in a BAPI. In other words, there is only ever exactly one internal interface structure for an external BAPI structure in a module. The name of this unique, internal interface structure is the name of the parameter in the API module.

Output

The program outputs the enhanced source code of the target include program appended with the new FORM.

Example

The function group 2099 contains a number of FORMS generated in this manner.

Concrete example

The selection:

Target include generated FORM L2099F11
Program of MAP2 function mod. L2099U08
Structure name in BAPI interf. CASESERVICE_CDATA
Structure name in API interf. SS_RNLSR
DDIC structure BAPI interface BAPI2099CDATA
DDIC structure API insterface RNLSR

Generates the FORM ADMAPT_CASESERVICE_CDATA at the end of the L2099F11 include program. In the process, the MAP2I_BAPI2099CDATA_TO_RNLSR is evaluated (the L2099U08 program). The BAPI parameter is called CASESERVICE_CDATA (see BAPI_CASESERVICE_CREATEMULT and BAPI_CASESERVICE_CHANGEMULT interfaces), the internal parameter SS_RNLSR (see the calls of the API modules ISH_CASESERVICE_CREATEMULTIPLE and ISH_CASESERVICE_CHANGEMULTIPLE in the source code of both BAPI modules mentioned above). The DDIC structure of the BAPI parameter is BAPI2099CDATA and that of the API parameter is RNLSR.

BAL Application Log Documentation   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3882 Date: 20240601 Time: 012006     sap01-206 ( 90 ms )