0000924105
2
8/10/2019 0000924105 http://slidepdf.com/reader/full/0000924105 1/2 SAP Note Header Data Symptom The ME_BSART_DET Business Add-In (BAdI) provides an additional function for determining the document type during the automatic conversion of purchase requisitions into purchase orders. Prerequisites You can use the function of the ME_BSART_DET BAdI only in the "new" Transaction ME59N. In the "old" Transaction ME59, the system does not run the source code. Standard settings l The ME_BSART_DET BAdI is not active (not implemented) in the standard system. l The BAdI is not filter-dependent. l The BAdI is not a multiple-use BAdI. Actions To activate the Business Add-In, you must create an active implementation. To do this, in the SAP menu, select Tools -> ABAP Workbench -> Utilities -> Business Add-In -> Implementation. You can find further information about the procedure in the SAP Library under Basis -> ABAP Workbench -> Changes to the SAP Standard -> Business Add-Ins -> Implementation of a Business Add-In. Documentation for the BSART_DETERMINE BAdI method. l Function You can use the BSART_DETERMINE method to define how the system is to determine the document type. l Result The method issues a document type that is copied to the EKKO table (EKKO-BSART). l Parameter ¡ IS_EBAN - Purchase requisition ¡ IF_GPSTYP - Grouping according to item category ¡ EF_BSART - Order type Output of the order type that is determined by the ME_BSART_DET BAdI ¡ EF_PSTYP - Item category in the purchasing document l Notes Do not make any database changes in the method. In this method, no COMMIT WORK statements must be executed. Other Terms - Reason and Prerequisites - 924105 - ME_BSART_DET: Documentation Version 2 Validity: 16.02.2006 - active Language English Released On 16.02.2006 13:56:34 Release Status Released for Customer Component MM-PUR-PO-GUI Userinterface - Purchase Orders Priority Recommendations / Additional Info Category Documentation error
-
Upload
altamirnunes -
Category
Documents
-
view
284 -
download
2
Transcript of 0000924105
8/10/2019 0000924105
http://slidepdf.com/reader/full/0000924105 1/2
SAP Note
Header Data
Symptom
The ME_BSART_DET Business Add-In (BAdI) provides an additional function for determining the documenttype during the automatic conversion of purchase requisitions into purchase orders.
Prerequisites
You can use the function of the ME_BSART_DET BAdI only in the "new" Transaction ME59N. In the "old"Transaction ME59, the system does not run the source code.
Standard settings
l The ME_BSART_DET BAdI is not active (not implemented) in the standard system.
l The BAdI is not filter-dependent.
l The BAdI is not a multiple-use BAdI.
Actions
To activate the Business Add-In, you must create an active implementation. To do this, in the SAPmenu, select Tools -> ABAP Workbench -> Utilities -> Business Add-In -> Implementation.
You can find further information about the procedure in the SAP Library under Basis -> ABAPWorkbench -> Changes to the SAP Standard -> Business Add-Ins -> Implementation of a Business Add-In.
Documentation for the BSART_DETERMINE BAdI method.
l Function
You can use the BSART_DETERMINE method to define how the system is to determine thedocument type.
l Result
The method issues a document type that is copied to the EKKO table (EKKO-BSART).
l Parameter
¡ IS_EBAN - Purchase requisition
¡ IF_GPSTYP - Grouping according to item category
¡ EF_BSART - Order type
Output of the order type that is determined by the ME_BSART_DET BAdI
¡ EF_PSTYP - Item category in the purchasing document
l Notes
Do not make any database changes in the method. In this method, no COMMIT WORK statementsmust be executed.
Other Terms
-
Reason and Prerequisites
-
924105 - ME_BSART_DET: Documentation
Version 2 Validity: 16.02.2006 - active Language English
Released On 16.02.2006 13:56:34
Release Status Released for Customer
Component MM-PUR-PO-GUI Userinterface - Purchase Orders
Priority Recommendations / Additional InfoCategory Documentation error
8/10/2019 0000924105
http://slidepdf.com/reader/full/0000924105 2/2
Solution
-
Validity
Software Component From Rel. To Rel. And Subsequent
SAP_APPL 470 470
500 500
600 600
