0% found this document useful (0 votes)
44 views4 pages

BAPI - PO - CREATE1: Technical Fields Available: Symptom

SAP Note 552189 addresses the limitations of BAPI_PO_CREATE1 and BAPI_PO_CHANGE regarding technical fields, which cannot currently be supplied, such as deactivating message determination or rounding. The document provides a solution involving the addition of import parameters and attributes to specific classes and structures to extend functionality. It recommends importing the note via a support package due to the complexity of the required corrections.

Uploaded by

fateme.soroush92
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
44 views4 pages

BAPI - PO - CREATE1: Technical Fields Available: Symptom

SAP Note 552189 addresses the limitations of BAPI_PO_CREATE1 and BAPI_PO_CHANGE regarding technical fields, which cannot currently be supplied, such as deactivating message determination or rounding. The document provides a solution involving the addition of import parameters and attributes to specific classes and structures to extend functionality. It recommends importing the note via a support package due to the complexity of the required corrections.

Uploaded by

fateme.soroush92
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

SAP Note

552189 - BAPI_PO_CREATE1: Technical fields available


Component: MM-PUR-PO-BAPI (BAPIs - Purchase order), Version: 7, Released On: 23.02.2005

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

Reason and Prerequisites


Up to now, this function was not provided.

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 46C 46C 549070 ME21N: Performance in the rounding MM-PUR-GF-QO

SAP_APPL 46C 470 527699 ME21N : error message M3 305. MM-PUR-PO-


GUI

SAP_APPL 470 470 548857 BAPI_PO_CHANGE: Dump RAISE_EXCEPTION in MM-PUR-PO-


GET_PO_SCHEDULES BAPI

SAP_APPL 470 470 549070 ME21N: Performance in the rounding MM-PUR-GF-QO

SAP_APPL 470 470 561507 BAPI_PO_CHANGE for services MM-SRV-BPI

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

SAP_APPL 46B SAPKH46B48

SAP_APPL 46C SAPKH46C39

SAP_APPL 470 SAPKH47006

P3A V3.0B SAPKI30B04

This document is causing side effects


SAP Note/KBA Title

809423 EnjoySAP PO BAPI: Technical parameters are not copied

639739 EnjoySAP order BAPI: Rounding is not executed

644460 In EXIT_SAPMM06E_012, i_vorga is not transferred

614936 ME21N: Info update indicator set in spite of default value

797454 BAPI_PO_CHANGE Technical fields overwritten with space

729620 ME21N: PO quantity update in BAnf incorrect

This document refers to


SAP Note/KBA Title

842320 BAPI_PO_CREATE1: Authorization check on PReq

797454 BAPI_PO_CHANGE Technical fields overwritten with space

658590 Mobilization item triggers messaging

639739 EnjoySAP order BAPI: Rounding is not executed

614936 ME21N: Info update indicator set in spite of default value

586672 Automatic rounding for purchase order change in WWP1

580225 Purchasing BAPIs: Conditions and pricing

561221 ME25: Checking the EFB parameter with call of ME21N

494759 BAPI_PO_CREATE1 and BAPI_PO_CHANGE: This is due to a redesig

1225535 BAPI_PO_CHANGE Pricing with B changes price after GR IR

This document is referenced by


SAP Note/KBA Title

2269588 ME21N: rounding in recursive cases

1225535 BAPI_PO_CHANGE Pricing with B changes price after GR IR

842320 BAPI_PO_CREATE1: Authorization check on PReq

580225 Purchasing BAPIs: Conditions and pricing

797454 BAPI_PO_CHANGE Technical fields overwritten with space

658590 Mobilization item triggers messaging


639739 EnjoySAP order BAPI: Rounding is not executed

494759 BAPI_PO_CREATE1 and BAPI_PO_CHANGE: This is due to a redesig

614936 ME21N: Info update indicator set in spite of default value

586672 Automatic rounding for purchase order change in WWP1

561221 ME25: Checking the EFB parameter with call of ME21N

You might also like