Kontakt

Ansicht
Dokumentation

PRF_OA_CREATE - BAdI: Create PRF Record for Document Type OA

PRF_OA_CREATE - BAdI: Create PRF Record for Document Type OA

Vendor Master (General Section)   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Localization Logistics (FI-LOC-LO)component.

Use this BAdI for the following functions:

  • Determine OA Document Types for which Procurement Reporting Framework(PRF) record should be created.
Use this BAdI to determine if the system should create a PRF record for a document type. In the standard scenario, the system allows creation and edition of a PRF record for PRF document type OA (02). However, you can define additional company specific PRF document types for which the system should allow creation and edition of a PRF record. This BAdI validates the Customizing data and determines if a PRF record should be created or not.
  • Perform validations for creation, edition of a PRF record
When a user creates or edits an Outline Agreement, the system performs standard validations based on the Customizing you have maintained in the Map Standard Document type to PRF Document view. However, if you want to define additional company specific validations, you can do so through this BAdI.
  • Prepare the data required for creating, editing of a PRF record
In the standard scenario, the system creates and edits a PRF record based on values such as contract, document number vendor information. However, if you want to define additional company specific data that the system should use to create and edit a PRF record, you can do so through this BAdI.

The following example explains the process by which you can maintain additional company specific document types. Additionally, it explains the process by which this BAdI determines whether a PRF record should be created or not.

  1. Maintain company specific PRF document types - You define the company specific PRF document types in the Define PRF Specific Document Typeview. Consider you have maintained two PRF document types as:
  • 01 – Pencil and Rubber having parent document type as 02 - Contract Vendor.

  • 04 – Electricity Expenses having no parent document type

  1. Map standard document type to PRF document type - You specify the mapping of standard document type and PRF doc type in the Map Standard Document type to PRF Document Typeview. Consider you have:
  • Standard document type P1 having business object type as BOR11 and sub type as S1

  • Standard document type P2 having business object type as BOR11 and sub type as S2

  • Standard document type P3 having business object type as BOR12 and sub type as S1

As per your company need, you want to create PRF record for sub type S1 and do not want to create PRF record for sub type S2. Maintain the following values in the Map Standard Document type to PRF Document Type view:
  • Standard document type P1 having business object type as BOR11 and sub type as S1 mapped to PRF document type 01 having parent document type as 02 - P1 BOR11 S1 01 02

  • Standard document type P3 having business object type as BOR12 and sub type as S1 mapped to PRF document type 04 having no parent document - P1 BOR11 S1 01 02

  1. Determine PRF record creation - The BAdI reads the document type of the source document and validates if a PRF record should be created based on the customizing maintained in the Map Standard Document type to PRF Document Type view. Consider that the document type of the source document (outline agreement) is P1. The BAdI will read Customizing data for P1 and determine the PRF document type and PRF parent document type. Next, the BAdI checks if a PRF record exists for the parent document type. If the PRF record does not exist, the system triggers the process for PRF record creation. If the PRF record exist, the system does not trigger the process for PRF record creation.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 5751 Date: 20240523 Time: 190654     sap01-206 ( 139 ms )