SAP Function BAPI_PO_CREATE1 - Create Purchase Order

Parameter Reference Type Length Default Optional Text
MEMORY_COMPLETE BAPIFLAG-BAPIFLAG C 1 X Hold Purchase Order if NOT Faulty
MEMORY_UNCOMPLETE BAPIFLAG-BAPIFLAG C 1 X Hold Purchase Order if Faulty
NO_AUTHORITY BAPIFLAG-BAPIFLAG C 1 X No Authorization Check
NO_MESSAGE_REQ BAPIFLAG-BAPIFLAG C 1 X No messages necessary
NO_MESSAGING BAPIFLAG-BAPIFLAG C 1 X No message determination
NO_PRICE_FROM_PO BAPIFLAG-BAPIFLAG C 1 X No Adoption of Price from Last Document
PARK_COMPLETE BAPIFLAG-BAPIFLAG C 1 X Park Document if NOT Faulty
PARK_UNCOMPLETE BAPIFLAG-BAPIFLAG C 1 X Park Document if Faulty
POADDRVENDOR BAPIMEPOADDRVENDOR u 1286 X Address of Vendor
POEXPIMPHEADER BAPIEIKP u 7 X Export Trade: Header Data
POEXPIMPHEADERX BAPIEIKPX u 2 X Foreign Trade: Change Bar: Header Data
POHEADER BAPIMEPOHEADER u 369 Header Data
POHEADERX BAPIMEPOHEADERX u 58 X Header Data (Change Parameter)
TESTRUN BAPIFLAG-BAPIFLAG C 1 X Test Indicator
VERSIONS BAPIMEDCM u 106 X Version Management

Parameter Reference Type Length Text
EXPHEADER BAPIMEPOHEADER u 369 Header Data
EXPPOEXPIMPHEADER BAPIEIKP u 7 Export Trade: Header Data
EXPPURCHASEORDER BAPIMEPOHEADER-PO_NUMBER C 10 Purchasing Document Number

Parameter Reference Length Optional Text
ALLVERSIONS BAPIMEDCM_ALLVERSIONS 233 X All Versions (Export Parameter)
EXTENSIONIN BAPIPAREX 990 X Customer's Own Fields (Import Parameters)
EXTENSIONOUT BAPIPAREX 990 X Customer's Own Fields (Export Parameters)
INVPLANHEADER BAPI_INVOICE_PLAN_HEADER 107 X Invoicing Plan Header Data
INVPLANHEADERX BAPI_INVOICE_PLAN_HEADERX 36 X Invoicing Plan Header Data (Change Parameter)
INVPLANITEM BAPI_INVOICE_PLAN_ITEM 119 X Invoicing Plan Item Data
INVPLANITEMX BAPI_INVOICE_PLAN_ITEMX 42 X Invoicing Plan Item Data (Change Parameter)
POACCOUNT BAPIMEPOACCOUNT 423 X Account Assignment Fields
POACCOUNTPROFITSEGMENT BAPIMEPOACCOUNTPROFITSEGMENT 87 X Reservation Profitability Segment: BAPI_PROFITABILITY_SEGMENT
POACCOUNTX BAPIMEPOACCOUNTX 50 X Account Assignment Fields (Change Parameter)
POADDRDELIVERY BAPIMEPOADDRDELIVERY 1322 X Addresses for Inward Delivery (Item)
POCOMPONENTS BAPIMEPOCOMPONENT 172 X BAPI Structure for Components
POCOMPONENTSX BAPIMEPOCOMPONENTX 36 X Update Information for Components in BUS2012 API
POCOND BAPIMEPOCOND 176 X Conditions (Items)
POCONDHEADER BAPIMEPOCONDHEADER 176 X Conditions (Header)
POCONDHEADERX BAPIMEPOCONDHEADERX 63 X Conditions (Header, Change Parameter)
POCONDX BAPIMEPOCONDX 63 X Conditions (Items, Change Parameter)
POCONTRACTLIMITS BAPIESUCC 90 X External Services: Contract Limits
POEXPIMPITEM BAPIEIPO 45 X Foreign Trade: Item Data
POEXPIMPITEMX BAPIEIPOX 13 X Foreign Trade: Change Parameter: Item Data
POITEM BAPIMEPOITEM 1230 X Item Data
POITEMX BAPIMEPOITEMX 165 X Item Data (Change Parameter)
POLIMITS BAPIESUHC 103 X External Services: Limits
POPARTNER BAPIEKKOP 14 X Partner
POSCHEDULE BAPIMEPOSCHEDULE 171 X Delivery Schedule
POSCHEDULEX BAPIMEPOSCHEDULX 35 X Delivery Schedule (Change Parameter)
POSERVICES BAPIESLLC 636 X External Services: Service Lines
POSERVICESTEXT BAPIESLLTX 158 X External Services: Service Long Text
POSHIPPING BAPIITEMSHIP 138 X BAPI Shipping Data for Stock Transport Orders
POSHIPPINGEXP BAPIMEPOSHIPPEXP 196 X Export Structure for Shipping Data
POSHIPPINGX BAPIITEMSHIPX 18 X BAPI Shipping Data Change Parameter
POSRVACCESSVALUES BAPIESKLC 40 X External Services: Account Assignment Distribution for Service Lines
POTEXTHEADER BAPIMEPOTEXTHEADER 153 X Header Texts
POTEXTITEM BAPIMEPOTEXT 153 X Item Texts
RETURN BAPIRET2 548 X Return Parameter
SERIALNUMBER BAPIMEPOSERIALNO 100 X Serial Numbers in Purchase Order BAPIs
SERIALNUMBERX BAPIMEPOSERIALNOX 14 X Change Parameter: Serial Number in Purchase Order BAPIs

Functionality
INCLUDE MMPUR_BAPI_OVERVIEW_CREATE OBJECT DOKU ID TX LANGUAGE EN

Functions in Detail
INCLUDE MMPUR_BAPI_ME21N_TABLES OBJECT DOKU ID TX LANGUAGE EN

Park and hold (Public Sector Management; PSM)
If you have activated the PSM, US Federal Government - GeneralFunctions 2 (PSM_USFED_CI_2) business function, park isavailable as well as hold, providing a further option for savingdocuments temporarily.
You can use this function module to control the conditions under whichpurchase orders can be put on hold, parked, or saved. First, the systemchecks whether the created document contains errors. In documents witherrors, the MEMORY_UNCOMPLETE and PARK_UNCOMPLETE parameters areevaluated. You control the system's behavior in documents that containno errors in the MEMORY_COMPLETE and PARK_COMPLETE parameters.
For more information, see the parameter documentation.
INCLUDE MMPUR_BAPI_ME21N_FUNC OBJECT DOKU ID TX LANGUAGE EN

Example
INCLUDE MMPUR_BAPI_ME21N_EXAMPLE OBJECT DOKU ID TX LANGUAGE EN

Help with Problems
RESET N1
INCLUDE MMPUR_BAPI_TROUBLESHOOTING OBJECT DOKU ID TX LANGUAGE EN

Customer Enhancements
INCLUDE MMPUR_BAPI_CUSTOMEREXTENSION OBJECT DOKU ID TX LANGUAGE EN

Further information
RESET N1
INCLUDE MMPUR_BAPI_ADD_INFO OBJECT DOKU ID TX LANGUAGE EN

Description
Header data of the purchase order created with the BAPI.

Description
Foreign trade data of the purchase order created with the BAPI (providedin advance for future development).

Description
Number of the purchase order created with the BAPI.

Description
You can use this parameter to control whether an error-free and completepurchase order is to be
put on hold or saved.
If the value of this parameter is 'X', the purchase order is put onhold.
If the value of this parameter is ' ', the purchase order is saved.

Park and hold (Public Sector Management; PSM)
If you have activated the PSM, US Federal Government - GeneralFunctions 2 (PSM_USFED_CI_2) business function, park isavailable as well as hold, providing a further option for savingdocuments temporarily. You use the MEMORY_COMPLETE and PARK_COMPLETEparameters to control when complete and correctly entered purchaseorders can be parked and when they can be saved.
The system checks the values of the two parameters and chooses thefurthest possible option of saving correct documents (put on hold -->park --> post):

  • If you want the option of putting correct purchase orders on hold, set
  • the value of the MEMORY_COMPLETE parameter to 'X'. The system checkswhether the PARK_COMPLETE parameter is also set.
    If the PARK_COMPLETE parameter also has the value 'X', the correctdocument is parked.
    If the PARK_COMPLETE parameter is not set, the correct document is puton hold.
    • If you do not want to allow correct purchase orders to be put on hold,
    • set the value of the MEMORY_COMPLETE parameter to ' '. The system checkswhether the PARK_COMPLETE parameter is set.
      If the PARK_COMPLETE parameter is not set either, the correct documentis saved.
      If the PARK_COMPLETE parameter also has the value 'X', the correctdocument is parked.
      The system proceeds according to the following logic:
      MEMORY_COMPLETE,, PARK_COMPLETE,, System Behavior
      X,, Empty,, Correct document is put on hold
      X,, X,, Correct document is parked
      Empty,, X,, Correct document is parked
      Empty,, Empty,, Correct document is saved

      Note
      You can control how the BAPI behaves in the case of a faulty orincomplete purchase order via the MEMORY_UNCOMPLETE parameter.

      Description
      You can use this parameter to specify whether a faulty or incompletepurchase order is to be
      put on hold.
      If the value of this parameter is 'X', the purchase order is put onhold.
      If the value of this parameter is ' ', the purchase order is notcreated.
      Park and hold (Public Sector Management; PSM)
      If you have activated the PSM, US Federal Government - GeneralFunctions 2 (PSM_USFED_CI_2) business function, park isavailable as well as hold, providing a further option for savingdocuments temporarily. You use the MEMORY_UNCOMPLETE and PARK_UNCOMPLETEparameters to control when incomplete and incorrectly entered purchaseorders can be parked and when they can be saved.
      First, the system checks which areas of the purchase order containincomplete or incorrect data.

      • If the purchase order contains consistency errors or errors in materials
      • management, the system does not read the PARK_UNCOMPLETE parameter.
        If the MEMORY_UNCOMPLETE parameter has the value 'X', the incorrectdocument is put on hold.
        If the MEMORY_UNCOMPLETE parameter has the value ' ', the incorrectdocument is not saved.
        • If the purchase order contains incorrect or incomplete budgeting data,
        • and no errors in materials management, the system reads thePARK_UNCOMPLETE and MEMORY_UNCOMPLETE parameters. The system chooses thefurthest possible option of saving incomplete documents (put on hold -->park).
          If the value of the PARK_UNCOMPLETE parameter is 'X', the purchase orderis parked, whether or not the MEMORY_UNCOMPLETE parameter is set.
          If the value of the PARK_UNCOMPLETE parameter is ' ', the system readsthe MEMORY_UNCOMPLETE parameter. If the MEMORY_UNCOMPLETE parameter hasthe value "X", the document is put on hold. If this parameter is notset, the purchase order is not saved.
          The system proceeds according to the following logic:
          MEMORY_UNCOMPLETE,, PARK_UNCOMPLETE,, System Behavior
          X,, Empty,, Document is put on hold
          X,, X,, Document is parked, if possible, and put on hold if not
          Empty,, X,, Document is parked, if possible, and not saved if not
          Empty,, Empty,, Document is not saved.

          Note
          You can control how the BAPI behaves in the case of an error-free andcomplete purchase order via the parameter MEMORY_COMPLETE.

          Description
          This parameter controls the authorization check.

          Value range
          'X' means: Do not carry out authorization check
          ' ' means: Carry out authorization check

          Default
          In the standard system, the parameter is initial.
          Note that this parameter can only influence the authorization check forpurchasing objects. An authorization check is still carried out at otherlevels (for example, at transaction level).

          Description
          This parameter controls the issuing of the system message that appearsif no messages (output versions of the PO document) could be generatedfor a purchase order.

          Value range
          'X' means: No messages (output versions of the PO document) areneeded; the system warning message is not issued
          ' ' means: Messages (output versions of the PO document) should begenerated; the system warning message is issued if no such messages havebeen generated.

          Default
          In the standard system, the parameter is initial.

          Description
          This parameter deactivates message determination for this invocation.

          Value range
          'X' means: Do not carry out message determination
          ' ' means: Carry out message determination

          Default
          In the standard system, the parameter is initial.

          Description
          This parameter controls the adoption of the price from the lastdocument.
          If no condition can be determined from the purchasing info record (noconditions have been maintained), the system adopts the conditions fromthe last purchase order stored in the purchasing info record.

          Value range
          'X' means: Price is not to be adopted from the last PO
          ' ' means: Price is to be adopted from the last PO if no price could befound in the master records.

          Default
          In the standard system, the parameter is initial.

          Description
          If you have activated the PSM, US Federal Government - GeneralFunctions 2 (PSM_USFED_CI_2) business function, you can parkpurchase orders whose budgeting data still needs to be checked. You usethe MEMORY_COMPLETE and PARK_COMPLETE parameters to control whencomplete and correctly entered purchase orders can be parked and whenthey can be saved.
          The system checks the values of the two parameters and chooses thefurthest possible option of saving correct documents (put on hold -->park --> post):

          • If you want the option of parking correct purchase orders in order to
          • check their budgeting data, set the value of the PARK_COMPLETE parameterto 'X'. Regardless of the value of the MEMORY_COMPLETE parameter,correct purchase orders are parked.
            • If you do not want to allow correct purchase orders to be parked, set
            • the value of the PARK_COMPLETE parameter to ' '. The system checkswhether the MEMORY_COMPLETE parameter is set.
              If the MEMORY_COMPLETE parameter is not set either, the correct documentis saved.
              If the MEMORY_COMPLETE parameter has the value 'X', the correct documentis put on hold.
              The system proceeds according to the following logic:
              PARK_COMPLETE,, MEMORY_COMPLETE,, System Behavior
              X,, Empty,, Correct document is parked
              X,, X,, Correct document is parked
              Empty,, X,, Correct document is put on hold
              Empty,, Empty,, Correct document is saved

              Default

              Note
              You can control how the BAPI behaves in the case of an incorrect orincomplete purchase order by using the PARK_UNCOMPLETE parameter.

              Description
              If you have activated the PSM, US Federal Government - GeneralFunctions 2 (PSM_USFED_CI_2) business function, you can parkpurchase orders whose budgeting data still needs to be checked. You usethe MEMORY_UNCOMPLETE and PARK_UNCOMPLETE parameters to control whenincomplete and incorrectly entered purchase orders can be parked andwhen they can be saved.
              First, the system checks which areas of the purchase order containincomplete or incorrect data.

              • If the purchase order contains consistency errors or errors in materials
              • management, the system does not read the PARK_UNCOMPLETE parameter.
                If the MEMORY_UNCOMPLETE parameter has the value 'X', the incorrectdocument is put on hold.
                If the MEMORY_UNCOMPLETE parameter has the value ' ', the incorrectdocument is not saved.
                • If the purchase order contains incorrect or incomplete budgeting data,
                • and no errors in materials management, the system reads thePARK_UNCOMPLETE and MEMORY_UNCOMPLETE parameters. The system chooses thefurthest possible option of saving incomplete documents (put on hold -->park).
                  If the value of the PARK_UNCOMPLETE parameter is 'X', the purchase orderis parked, whether or not the MEMORY_UNCOMPLETE parameter is set.
                  If the value of the PARK_UNCOMPLETE parameter is ' ', the system readsthe MEMORY_UNCOMPLETE parameter. If the MEMORY_UNCOMPLETE parameter hasthe value "X", the document is put on hold. If this parameter is notset, the purchase order is not saved.
                  The system proceeds according to the following logic:
                  PARK_UNCOMPLETE,, MEMORY_UNCOMPLETE,, System Behavior
                  X,, Empty,, Document is parked, if possible, and not saved if not
                  X,, X,, Document is parked, if possible, and put on hold if not
                  Empty,, X,, Document is put on hold
                  Empty,, Empty,, Document is not saved.

                  Default

                  Note
                  You can control how the BAPI behaves in the case of a correct andcomplete purchase order by using the PARK_COMPLETE parameter.

                  Description
                  INCLUDE MMPUR_BAPI_POADDRVENDOR OBJECT DOKU ID TX

                  Description
                  This parameter contains foreign trade data for the PO header. Pleasealso note the table parameter POEXPIMPITEM, which contains the foreigntrade data for the PO items.

                  Description
                  Provided for future development.

                  Description
                  INCLUDE MMPUR_BAPI_POHEADER OBJECT DOKU ID TX

                  Description
                  INCLUDE MMPUR_BAPI_POHEADERX OBJECT DOKU ID TX
                  INCLUDE SD_BAPI_TESTRUN OBJECT DOKU ID TX

                  Description
                  This parameter contains data for Version Management.

                  Description
                  Complete list of all versions of this purchase order.
                  INCLUDE MMPUR_BAPI_EXTENSIONIN OBJECT DOKU ID TX
                  INCLUDE MMPUR_BAPI_EXTENSIONOUT OBJECT DOKU ID TX

                  Description
                  INCLUDE MMPUR_BAPI_POACCOUNT OBJECT DOKU ID TX
                  INCLUDE MMPUR_BAPI_POACCOUNTPROFIT OBJECT DOKU ID TX

                  Description
                  INCLUDE MMPUR_BAPI_POACCOUNTX OBJECT DOKU ID TX

                  Description
                  INCLUDE MMPUR_BAPI_POADDRDELIVERY OBJECT DOKU ID TX

                  Description
                  Components for subcontracting items with update indicator (Insert,Update, Delete, Replace).

                  Description
                  Change parameter for components for subcontracting items.

                  Description
                  INCLUDE MMPUR_BAPI_POCOND OBJECT DOKU ID TX

                  Description
                  Analogically to the item conditions, enter '00000' instead of the itemnumber.

                  Description
                  You can use this parameter to specify which fields of the parameterPOCONDHEADER are change-relevant.

                  Description
                  INCLUDE MMPUR_BAPI_POCONDX OBJECT DOKU ID TX

                  Description
                  INCLUDE MMPUR_BAPI_POCONTRACTLIMITS OBJECT DOKU ID TX

                  Description
                  Include: This table contains the foreign trade data (item). Thiscomprises:

                  • Business transaction type (nature of transaction) for foreign trade

                  • Export/import procedure for foreign trade

                  • Country of origin of material (CIC origin)

                  • Region of origin of material (CIC origin)

                  • Commodity code/import code for foreign trade

                  • Country of dispatch for foreign trade
                  • Description
                    Corresponds to the function of other change parameters.

                    Description
                    INCLUDE MMPUR_BAPI_POITEM OBJECT DOKU ID TX

                    Description
                    INCLUDE MMPUR_BAPI_POITEMX OBJECT DOKU ID TX

                    Description
                    INCLUDE MMPUR_BAPI_POLIMITS OBJECT DOKU ID TX

                    Description
                    This structure enables you to maintain partners. Only one partner maybe specified per partner role. If you specify more than this, thesystem issues an error message. It is also not possible to change thepartner "vendor". This role is predefined via the PO header vendor.
                    The partner roles can be defined inCustomizing. You can also define the language-dependent keys for thepartner roles. This makes it possible to specify the partner roles indifferent languages (example: ordering address, language EN -> partnerrole OA; language DE -> partner role BA)
                    Parameter: POPARTNER
                    PARTNERDESC,,=,,OA
                    LANGU,,=,,EN
                    BUSPARTNO,,=,,0000001000
                    PARTNERDESC,,=,,WL
                    LANGU,,=,,DE
                    BUSPARTNO,,=,,0000001100

                    Description
                    INCLUDE MMPUR_BAPI_POSCHEDULE OBJECT DOKU ID TX

                    Description
                    INCLUDE MMPUR_BAPI_POSCHEDULEX OBJECT DOKU ID TX

                    Description
                    INCLUDE MMPUR_BAPI_POSERVICES OBJECT DOKU ID TX

                    Description
                    INCLUDE MMPUR_BAPI_POSERVICESTEXT OBJECT DOKU ID TX

                    Description
                    This structure represents all fields that are changeable within theshipping data for stock transport orders.

                    Description
                    This structure contains all data of the shipping data from a stocktransfer or returns item and represents the external representation oftable EKPV (shipping data).

                    Description
                    Change parameter for components for subcontracting items.

                    Description
                    INCLUDE MMPUR_BAPI_POSRVACCESSVALUES OBJECT DOKU ID TX

                    Description
                    This parameter enables you to create header texts. The assignment ofthe text is carried out via a text ID. This identification numberconsists of the ID for the document type (a PO has F) and the text IDitself (example: F01). You can find these values in Customizing underText Types for Header Texts in the nodeTexts for Purchase Orders .
                    In the case of item texts, PO_ITEM contains the item number of thepurchasing document (in the case of header texts, the field PO_NUMBERis not to be populated).
                    If texts are to be changed with the Change method, only the completetext can be replaced. It is not possible to delete just one line, forexample.
                    4. Examples of population of BAPI_PO_CREATE1 interface:
                    Parameter: POTEXTHEADER
                    PO_NUMBER
                    PO_ITEM,,=,,00000
                    TEXT_ID,,=,,F01
                    TEXT_FORM,,=,,*
                    EXT_LINE,,=,,HEADER TEXT
                    Parameter: POTEXTITEM
                    PO_NUMBER
                    PO_ITEM,,=,,00010
                    TEXT_ID,,=,,F05
                    TEXT_FORM,,=,,*
                    EXT_LINE,,=,,ITEM TEXT, ITEM 00010

                    Description
                    Analogically to header texts.

                    Description
                    INCLUDE BAPI_TABLE OBJECT DOKU ID TX
                    INCLUDE MMPUR_604_BAPI_SERNO OBJECT DOKU ID TX
                    The serial number always refers to one schedule line of a document item.If no schedule line is recorded, the program implicitly assumes thefirst line with the number 0001. The serial number always refers to thebase unit of measure and not explicitly the purchase order unit.
                    If you order one dozen of a material to be serialized, and the base unitis piece, 12 serial numbers must be recorded.
                    You can use the DELETE_IND to delete assigned serial numbers.
                    If you want to partially convert a serialized purchase requisition,transfer the serial numbers that you do not want copied to the purchaseorder item (DELETE_IND = X).
                    INCLUDE MMPUR_604_BAPI_SERNOX OBJECT DOKU ID TX

1230233BAPI terminates with runtime error DYNPRO_SEND_IN_BACKGROUND
1621335Follow-on Note of Note 1596230
1610288Follow-on Note of Note 1344324
1488158Error MEPO 046 for items with discount in kind
539950BAPI_PO_CREATE1: n condition records for a condition type
197958BAPIs for purchase orders: Missing functions
1555257No direct postings can be made to G/L acct in CoCode error
1547593Accounting Data not adopted by BAPI
1447024Accounting and/or Schedule Data not adopted by BAPI
1464524Error ME083 unexpected during PO transfer
499626FAQ: BAPIs in the service procurement
1482028BAPI_PO_CREATE1: MEPO 047 when changing account assignment
1455040error ME 083 when creating PO via BAPI_PO_CREATE1
1465073Accounting data not adopted by BAPI
1462262Dump OBJECTS_OBJREF_NOT_ASSIGNED when creating deleted item
1435989Account assignment data not transferred from interface
1387511Price determination type always reset when PO created
1061443Incorrect cost assignment for backend PO with services
1160754Update exception for BAPI_PO_CREATE1 in test mode
1147338Service PO: unjustified budget error as of delivery end date
767284SE518 occurs although account assignment is supplied to BAPI
1241637Consultation for purchase order in EHS-WA (using PO BAPIs)
1168174Incorrect value of /AFS/SZIN and /AFS/CTIN in EKET
399791Enjoy-BAPI_PO...: Condition values are not transferred
891356BAPI EnjoySAP: Exception Raise Failure
1111389Messages are missing when you use the new purcahsing BAPI
1086345BAPI_PO_CREATE1: PO price overwritten by requisition price
1025130Success message missing in the BAPI for purchase orders
1027212Follow-on Note of Note 957718
850409EnjoySAP order BAPI: Messages without class and number
932236BAPI_PO_CREATE1: Purchase order price unit not transferred
982032PO create using BAPI or ME21N does not consider DECAN/ANDEC
1002406BAPI_PO_CHANGE: Cannot change the address type
990946BBPSC01: Accounting error during PO creation
938653BAPI_PO_CREATE1: Creation of locked item
952504Transfer error: ME 083: "Enter functional area"
758884BAPI_PO_CREATE1: Funds reservation and technical fields
942946BAPI_PO_CREATE1 does not copy price from SRM
853970BAPI_PO_CREATE1: Net price is not transferred
938982Shopping cart: Error when creating a purchase order
736770EnjoySAP order BAPI: Customer enhancemnt CI_COBL not changed
910990BAPI_PO_CREATE1: ME 083 "Bitte Sachkonto eingeben"
910636BAPI_PO_CREATE1: Error from account assignment check
900620E WY017 Partner not created for Purch.Org.(BAPI_PO_CREATE1)
893674BAPI_PO_CREATE1: Dump OBJECTS_OBJREF_NOT_ASSIGNED
884889Incorrect delivery address on purchase orders (Action ORD1)
419838BAPI_PO_... : Foreign trade data (import/export)
707090BAPI_PO_CREATE1: External number is not transferred
842320BAPI_PO_CREATE1: Authorization check on PReq
552189BAPI_PO_CREATE1: Technical fields available
530900BAPI_PO_CREATE1: External PurchOrder number not transferred
809423EnjoySAP PO BAPI: Technical parameters are not copied
793583Tax Jurisdiction code from address number
751130BAPI_PO_CREATE1: Status is always set to 9
661689Authorization check to transaction code in BAPI
753694BAPI_PO_CREATE1 update termination for header conditions
736960BAPI_PO_CREATE1: EKKO-LOGSY not filled
741822TAX. Problems w/ Backend tax indicator and jurisdiction code
675523Conditions are copied from Last Purchase Order
711876Field Grant_nbr is not set in new Purchase Order
544085BAPI_PO_CREATE1/CHANGE: does not copy all data (2)
662464BAPI_PO_CREATE1: No 'on hold' of incorrect purchase orders
639739EnjoySAP order BAPI: Rounding is not executed
372976BAPI_PO_CREATE1 not yet released officially
494759BAPI_PO_CREATE1 and BAPI_PO_CHANGE: This is due to a redesig
439110Enjoy PO BAPI: Conditions
428621EnjoySAP purchase order BAPIs - price det. & cond. change
410491BAPI_PO_CREATE1: Customer enhancements incorrct from 2. item
393819BAPI: Messages outputted for PO on hold
588647EBP Catalog Price Not Considered in Backend PO
503910BAPI_PO_CHANGE/BAPI_PO_CREATE1: Adding items
586672Automatic rounding for purchase order change in WWP1
574460BAPI_PO_CREATE1: Externl purchase order numbr not transferrd
581302Delivery Date is Not Transferred to Backend PO
552598BAPI_PO_CREATE1: KI292 in account assignment
489799BAPI_PO_CREATE1 does not copy all data from the interface
528252 Shopping Cart generates contract instead POs at backend
527614BAPI_PO_CREATE1 errors by creation of backend PO
527297Shortdump During Backend PO Creation with BAPI_PO_CREATE1
420049BAPI_PO_CREATE1 terminates with error 00151 or VD399
418683BAPI_PO_CREATE1: Item numbers external/internal
491835BAPI_PO_CREATE1 / CHANGE -> Implementation of texts
375886BAPI: Error analysis for BAPIs in purchasing
492252Street name with more than 40 characters
390742Customer enhancements not transferred
366461Enjoy BAPI: Field not transferred / error message MEPO019
351132ME21N copy purchase order: requisitioner/requester lost
376424BAPI_PO_CREATE1: Error messages for parked POs
351262Enjoy BAPI: error handling.
356002Enjoy BAPI: Transferred delivery date ignored
353626PO generation performance from allocation table
180172BAPI_PO_CREATE: Transfer of an address number
323152Enjoy BAPI: Implementation of customer enhancements
317877Enjoy BAPI: profitability segment