BAPI - PO - CREATE1: Technical Fields Available: Symptom
BAPI - PO - CREATE1: Technical Fields Available: Symptom
Symptom
Technical fields cannot be supplied with BAPI_PO_CREATE1. For example, it is not possible to
deactivate the message determination or rounding.
The same problem occurs if you try to generate new items with function module
BAPI_PO_CHANGE.
Other Terms
BUS2012, BAPI_PO_CREATE1, BAPI_PO_CHANGE, PurchaseOrder, CreateFromData,
Change, PurchaseOrder.CreateFromData1, PurchaseOrder.Change,
NO_ROUNDING, NO_MESSAGING, NO_MESSAGE_REQ, NO_AUTHORITY,
NO_PRICE_FROM_PO
Solution
Due to the complexity of the correction we recommend that you import this note by support
package because a number of interfaces and table definitions have to be extended.
If you want to implement the note manually, follow the instruction.
1. Add the following import parameters to the interfaces of BAPI_PO_CREATE1 and
BAPI_PO_CHANGE.
Parameter name Type spec. Reference type Opt. Pass value
a) NO_MESSAGING LIKE BAPIFLAG-BAPIFLAG X X
b) NO_MESSAGE_REQ LIKE BAPIFLAG-BAPIFLAG X X
c) NO_AUTHORITY LIKE BAPIFLAG-BAPIFLAG X X
d) NO_PRICE_FROM_PO LIKE BAPIFLAG-BAPIFLAG X X
2. Add 4 attributes to class CL_PO_HEADER_HANDLE_MM
Attribute Type Visibility Type spec. Reference type
==============================================================
a) NO_MESSAGING Instance Public TYPE MMPUR_BOOL
b) NO_MESSAGE_REQ Instance Public TYPE MMPUR_BOOL
c) NO_AUTHORITY Instance Public TYPE MMPUR_BOOL
d) NO_PRICE_FROM_PO Instance Public TYPE MMPUR_BOOL
3. You must add the following import parameter to function module MEPO_DOC_PROCESS.
Parameter name Type spec. Ref.field Opt. Short text
==============================================================
a) IM_NO_MESSAGING TYPE XFELD X No message determination
b) IM_NO_MESSAGE_REQ TYPE XFELD X No messages necessary
c) IM_NO_AUTHORITY TYPE XFELD X No authorization check
d) IM_NO_PRICE_FROM_PO TYPE XFELD X No price from last purchase
order
Below is an explanation of the extension of the item structures in order to prevent rounding
4. Enhancement of structure BAPIMEPOITEM (direct to CALCTYPE)
Component Component type
a) NO_ROUNDING NO_ROUNDING
5. Enhancement of structure BAPIMEPOITEMX (direct to CALCTYPE)
Component Component type
a) NO_ROUNDING BAPIUPDATE
6. Enhancement of structure MEPOITEM_DATA (direct to CALCTYPE)
Component Component type
a) NO_ROUNDING NO_ROUNDING
7. Enhancement of structure MEPOITEM_DATAX (direct to CALCTYPE)
Component Component type
a) NO_ROUNDING BAPIUPDATE
8. Implement the attached correction instructions. Note that, for Release 4.6C, the
correction is only possible as of Support Package SAPKH46C33 (Note 494759).
Manual Activities
Software Components
Software Component And subsequent
SAP_APPL
SAP_APPL
SAP_APPL
P3A
Correction Instructions
Software Component Number of Correction Instructions
SAP_APPL 2
Prerequisites
Software From To SAP Title Component
Component Note/KBA
SAP_APPL 46A 46C 300252 ME21N/ME22N:Repeated rounding after incorrct roundg MM-PUR-PO-
GUI
SAP_APPL 46B 46C 549076 ME21N: header texts deleted if plant in pers. settings MM-PUR-GF-
TEXT
SAP_APPL 470 470 569317 Function group 2012: Syntax error in unicode systems MM-PUR-PO-
BAPI
SAP_APPL 470 470 579205 Dump due to incorrect interface: UESLL instead of ESLL MM-SRV
SAP_APPL 470 470 582252 BAPI_PO_CREATE1/..._CHANGE: Header conditions are MM-PUR-PO-
incorrect BAPI
SAP_APPL 470 470 589066 BAPI_PO_CHANGE: Incorrect account assignment to network MM-PUR-PO-
BAPI
Support Package
Software Component Version Support Package