Custom Logic(BAdIs)/Extensibility in Purchase Order Output Management

[SivaKumarSeelam]

The following custom logic's are available for purchase order outputs:

• MMPUR_PO_STD_HEADER_TEXT - Determine Standard Text Sent for Purchase Order Output Header

• MMPUR_PO_STD_ITEM_TEXT- Determine Standard Text Sent for Purchase Order Output Item

• MMPUR_PO_OUTPUT_TEXT- Determine Output Language for Purchase Order Output Standard Text

• MMPUR_PURCHASE_ORDER_SHIP_TYPE- Enrich shipping type in purchase order output

• APOC_ADD_EMAIL_RECIPIENTS- BAdI: Addition of Email Recipients
  

1. MMPUR_PO_STD_HEADER_TEXT - Determine Standard Text Sent for Purchase Order Output Header: 

With this custom logic, you can: 

1. Add new Purchase Order Standard Header Texts in addition to the Purchase Order Standard Header Texts configured in the configuration. 
2. Replace/Modify the existing Purchase Order Standard Header Texts configured in the SSCUI with a new Purchase Order Standard Header Texts. 
3. Delete the existing Purchase Order Standard Header Texts configured in the SSCUI. 
   

Below is an example to add new header standard text using BAdi: 

With the above BAdi implementation, along with the Standard Texts maintained in the SSCUI-102270, standard text (ZSTANDARD_TEXT_OUTPUT_HEADER) added in the BAdi Implementation will also be available in the form data provider (data source).   

If the corresponding field is created and bind with data source in the custom form template, standard texts will be available on purchase order output form. 

2. MMPUR_PO_STD_ITEM_TEXT- Determine Standard Text Sent for Purchase Order Output Item 

Using this BAdi, it is possible to: 

1. Add new Purchase Order Item Standard Texts in addition to the Purchase Order Item Standard Texts configured in the SSCUI.
2. Replace/Modify the existing Purchase Order Item Standard Texts configured in the SSCUI with a new Purchase Order Item Standard Texts.
3. Delete the existing Purchase Order Item Standard Texts configured in the SSCUI. 

Below is an example to delete Item standard text using BAdi: 

With the above BAdi implementation, out of all the standard texts maintained in the SSCUI-102270, standard text (STEXT_1010_1010_1010) deleted in the BAdi Implementation will not be available in the form data provider (data source).   

Though, corresponding field is created and bind with data source in the custom form template, standard texts will not be available on purchase order output form (since deleted from BAdi implementation). 

Note: Standard texts mapping entry from the BAdi are validated and processed to print on the output. If validation is not successful, the standard text mapping entry from the BAdi will be ignored. 

3. MMPUR_PO_OUTPUT_TEXT- Determine Output Language for Purchase Order Output Standard Text 

Using this BAdi, it is possible to overwrite the language (configured in SSCUI) in which standard text will be printed on the purchase order output form.  

Below is an example to modify the standard text language to purchase order language if both form template language and purchase order language are different. 

With the above implementation, the standard texts configured in SSCUI, will be always printed in purchase order language. 

4. MMPUR_PURCHASE_ORDER_SHIP_TYPE- Enrich shipping type in purchase order output

In a Purchase Order, Shipping Type is available at header and item.  

Using this BAdi, it is possible to: 

1. Modify existing header shipping type in purchase order.
2. Control the visibility (show or hide) of item shipping type in purchase order. 

Below is the example to  

1. print shipping type at header and hide at item if all the items have the same shipping type. 
2. print first item shipping type at header and item level shipping types at each item, if all the items don’t have the same shipping type. 

5. APOC_ADD_EMAIL_RECIPIENTS- BAdI: Addition of Email Recipients

Using this BAdi, it is possible to send purchase order email output to multiple recipients.

For example: 
In a scenario, where email output must be sent to Purchaser along with Supplier, this BAdi can be implemented to fill the changing parameter with Purchaser and Supplier EMAIL address. 

To achieve this, Output Parameter Determination must be configured with the expression “Add email recipients from custom logic” and the BAdi must be implemented as shown below.

With this, once the EMAIL outputs are generated and completed, both purchase and supplier will receive the EMAIL Outputs 

Note: Please make sure, you have implemented the filter condition OUTPUTCONTROLAPPLOBJECTTYPE = PURCHASE_ORDER 

Frequently Asked Questions:

Q1.  Is it possible to change any texts in purchase order output using BAdi’s Determine Standard Text Sent for Purchase Order Output i) Header and ii)Item

Ans: No. It is possible to modify only Standard Texts which are maintained in “manage text” app. 

Q2. Why is the standard text not printed on the output? 

Ans: Please check if the required standard text is available/maintained in the expected language. For more details on the standard text language please refer to Q4 in Standard Texts in Purchase Order outputs  

Q3. Which language text is picked of language BAdI is not implemented?  

Ans:  please refer to Q4 in Standard Texts in Purchase Order outputs