SAP ABAP IMG Activity ADS2KIPUPL_S_PARSER (Implement Customer Extensions to S File Parser)
Hierarchy
☛
ECC-DIMP (Software Component) DIMP
⤷
IS-AD-SPC (Application Component) Specification 2000
⤷
ADS2KIPUPL_AL (Package) SPEC 2000 Initial Provisioning Upload: File Readers/Parsers

⤷

⤷

IMG Activity
ID | ADS2KIPUPL_S_PARSER | Implement Customer Extensions to S File Parser |
Transaction Code | S_KA5_12001155 | IMG activity: ADS2KIPUPL_S_PARSER |
Created on | 20020509 | |
Customizing Attributes | ADS2KIPUPL_S_PARSER | Implement customer extensions to S File Parser |
Customizing Activity | ADS2KIPUPL_S_PARSER | Implement customer extensions to S File Parser |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ADS2KIPUPL_S_PARSER |
You use this Business Add-In (BAdI) to handle S File record types that are not part of SPEC2000. It needs to be used in conjunction with the S File Reader BAdI (ADS2KIPUPL_S_READER).
SAP provides the following methods:
- INITIALIZE_EXTENSION_DATA : Use this method to accept the data that was read in the S File reader BAdI. The interface is:
- IS_PART_KEY: Key fields of the part.
- IT_ENCODED_DATA : Imports data that was encoded in the reader BAdI �ADS2KIPUPL_S_READER�. Use function module �SPTA_INDX_PACKAGE_DECODE� to decode data to the appropriate structures.
- PROCESS_PNRV_EC_SEGMENT: Use this method when the customer specific Explanation Codes (EC) need to be implemented in the PNRV Segment. The list of customer valid ECs need to be passed to the calling application using the method GET_VALID_ECS_PNRV. REJECT_SEGMENT is the exception which rejects the segment.
- PROCESS_ADRV_EC_SEGMENT: Use this method when the customer specific Explanation Codes (EC) need to be implemented in the ADRV Segment. The list of customer valid ECs need to be passed to the calling application using the method GET_VALID_ECS_ADRV. REJECT_SEGMENT is the exception which rejects the segment.
If the BAdI is not active, all non-SPEC2000 compliant ECs are recognized as errors.
- PROCESS_EXTENSION_DATA : Use this method at the end of processing for each part. The interface is:
- IS_API_IF: A part information in structures that resemble the API Interface.
- ET_MESSAGES: Format in which the messages must be raised.
- CT_EXTENSION: Customer data needs to be populated in this parameter. The API for the part update (API_S2K_IP_PART_UPDATE) then receives this customer data. The user needs to implement the BADI for Part API (ADS2KIPUPL_PART_API) for handling the data.
- REJECT_PART: Exception. Rejects the part.
Example
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | ADS2KIPUPL_S_PARSER | 0 | KAD0000015 | Provisioning |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20021112 |
SAP Release Created in | 471 |