What and Which are the Mandatory fields in a Purchase Order?

Please advise how I can check what the Mandatory fields are in a purchase order and which fields are not Mandatory ?
Also, Please advise where this information can be found in the manual?
Thanks in advance.
Edited by: Darpal Thiarha on Feb 26, 2008 3:49 PM

Hi,
mandatory fields are:
vendor
docdate
delivery date
and other fields you may test in sbo_transactionnotification procedure.
I don`t think that this is written in manual, you have to test to add the document with few fields filled and check it.
Petr

Similar Messages

What are the Mandatory Fields in Transaction ME51

Hello Seniors,
I have a requirement about purchase order creation. In this process, I am using the BAPI named " BAPI_PO_CREATE1 ". I have passed all the fields but when I debug and look into the internal tables, I couldn't find certain records. I even debugged " bapiret2" and I see an error which reads "" All mandatory fields are missing"". I have even created a PO in ME51 and found out the mandatory fields but in vain. BAPIRET2 still says, there are some more mandatory fields missing. I need to know what are all the mandatory fields to create a Purchase order using TCODE - ME51.
Your reply is most awaited and rewarded.
Thanks and Regards,
MARKIV

hi ,
Functionality
Function module BAPI_PO_CREATE1 enables you to create purchase orders. The BAPI uses the technology behind the Enjoy purchase order transaction ( ME21N).
Alternatively, the IDoc type PORDCR1 is available. The data from this IDoc automatically populates the interface parameters of the function module BAPI_PO_CREATE1.
Functionality in Detail
Authorization
The following authorization objects are checked when an Enjoy purchase order is created (activity 01):
M_BEST_BSA (document type in PO)
M_BEST_EKG (purchasing group in PO)
M_BEST_EKO (purchasing organization in PO)
M_BEST_WRK (plant in PO)
Controlling adoption of field values via X bar
For most tables, you can determine via your own parameters in the associated X bar in each case (e.g. PoItemX) whether fields are to be set initial, values inserted via the interface, or default values adopted (e.g. from Customizing or master records) (for example, it is not mandatory to adopt the material group from an underlying purchase requisition - you can change it with the BAPI).
Transfer
Header data
The header data of the Enjoy purchase order is transferred in the table PoHeader.
Item data
The item data of the Enjoy purchase order is stored in the table PoItem (general item data). The delivery schedule lines are stored in the table PoSchedule.
Use the table PoAccount to specify the account assignment information. If account assignments have been specified for services and limits, you show the relevant account assignment line in PoAccount in the table PoSrvAccessValues via the package number of the service or the limit.
Services and limits
Services, free limits and limits with contract reference can be specified in the tables PoServices, PoLimits, and PoContractLimits.
Conditions
Conditions are transferred in the table PoCond; header conditions in the table PoCondHeader. Price determination is reinitiated via the parameter CALCTYPE in the table PoItem.
Vendor and delivery address
The vendor's address can be specified individually in the table PoAddrVendor; the delivery address in the table PoAddrDelivery. If you do not make any individual specification, the fields will be populated via the central address managementfacility.
Note
In this method, the following restrictions apply with regard to addresses:
Addresses can only be created with this method - they cannot be changed. You can only change address data with the method BAPI_ADDRESSORG_CHANGE.
When you create addresses, they are not checked by the method. An Enjoy purchase order may therefore contain faulty address data.
Partner roles
The partners can be maintained individually via the table PoPartner (with the exception of the partner role "vendor").
Import/export data
Import/Export data can be specified per item in the table PoExpImpItem. Foreign trade data can only be transferred as default data for new items.
Texts
Header and item texts can be transferred in the tables PoTextHeader and PoTextItem. Texts for services are imported in the table PoServicesText.
Version Management
You can make use of the Version Management facility via the table AllVersions.
Return
The PO number is returned in the parameter ExpPurchaseOrder. In addition, all information except the service and export/import tables is placed in the output structures.
Return messages
Messages are returned in the parameter Return. This also contains information as to whether interface data has been wrongly or probably wrongly (heuristical interface check) populated. If a PO has been successfully created, the PO number is also placed in the return table with the appropriate message.
Example
Example of population of BAPI interface in the Function Builder
Parameter: POHEADER
COMP_CODE = 1000
DOC_TYPE = NB
ITEM_INTVL = 00001
VENDOR = 0000001000
PMNTTRMS = 0001
PURCH_ORG = 1000
PUR_GROUP = 001
CURRENCY = EUR
Parameter: POHEADERX
COMP_CODE = X
DOC_TYPE = X
ITEM_INTVL = X
VENDOR = X
PMNTTRMS = X
PURCH_ORG = X
PUR_GROUP = X
Parameter: POITEM
PO_ITEM = 00001
MATERIAL = 100-100
PLANT = 1000
STGE_LOC = 0001
QUANTITY = 15.000
TAX_CODE = V0
ITEM_CAT = 0
ACCTASSCAT = K
Parameter: POITEMX
PO_ITEM = 00001
MATERIAL = X
PLANT = X
STGE_LOC = X
QUANTITY = X
TAX_CODE = X
ITEM_CAT = X
ACCTASSCAT = X
Parameter: POSCHEDULE
PO_ITEM = 00001
SCHED_LINE = 0001
DELIVERY_DATE = 02.12.2002
QUANTITY = 6.000
PO_ITEM = 00001
SCHED_LINE = 0002
DELIVERY_DATE = 03.12.2002
QUANTITY = 5.000
PO_ITEM = 00001
SCHED_LINE = 0003
DELIVERY_DATE = 04.12.2002
QUANTITY = 4.000
Parameter: POSCHEDULEX
PO_ITEM = 00001
SCHED_LINE = 0001
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0002
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0003
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
Parameter: POACCOUNT
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = 15.000
GL_ACCOUNT = 0000400000
COSTCENTER = 0000001000
CO_AREA = 1000
Parameter: POACCOUNTX
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = X
GL_ACCOUNT = X
COSTCENTER = X
CO_AREA = X
Parameter: POCOND
ITM_NUMBER = 000001
COND_ST_NO = 001
COND_TYPE = PB00
COND_VALUE = 79.900000000
CURRENCY = EUR
CURRENCY_ISO = EUR
COND_UNIT = KG
COND_P_UNT = 1
CHANGE_ID = U
Parameter: POCONDX
ITM_NUMBER = 000001
COND_ST_NO = 000
ITM_NUMBERX = X
COND_TYPE = X
COND_VALUE = X
CURRENCY = X
CHANGE_ID = X
Parameter: POPARTNER
PARTNERDESC = OA
LANGU = EN
BUSPARTNO = 0000001100
PARTNERDESC = GS
LANGU = EN
BUSPARTNO = 0000001200
PARTNERDESC = PI
LANGU = EN
BUSPARTNO = 0000001000
Help in the Case of Problems
1. Note 197958 lists answers to frequently asked questions (FAQs). (Note 499626 contains answers to FAQs relating to External Services Management.)
2. If you have detected an error in the function of a BAPI, kindly create a reproducible example in the test data directory in the Function Builder (transaction code SE37). Note 375886 tells you how to do this.
3. If the problem persists, please create a Customer Problem Message for the componente MM-PUR-PO-BAPI, and document the reproducible example where necessary.
Customer Enhancements
The following user exits (function modules) are available for the BAPI BAPI_PO_CREATE1:
EXIT_SAPL2012_001 (at start of BAPI)
EXIT_SAPL2012_003 (at end of BAPI)
The following user exits (function modules) are available for the BAPI BAPI BAPI_PO_CHANGE:
EXIT_SAPL2012_002 (at start of BAPI)
EXIT_SAPL2012_004 (at end of BAPI)
These exits belong to the enhancement SAPL2012 (see also transaction codes SMOD and CMOD).
There is also the option of populating customer-specific fields for header, item, or account assignment data via the parameter EXTENSIONIN.
Further information
1. Note 197958 contains up-to-date information on the purchase order BAPIs.
2. If you test the BAPIs BAPI_PO_CREATE1 or BAPI_PO_CHANGE in the Function Builder (transaction code SE37), no database updates will be carried out. If you need this function, please take a look at Note 420646.
3. The BAPI BAPI_PO_GETDETAIL serves to read the details of a purchase order. The BAPI cannot read all details (e.g. conditions). However, you can use the BAPI BAPI_PO_CHANGE for this purpose if only the document number is populated and the initiator has change authorizations for purchase orders.
4. Frequently used BAPIs for purchase orders are BAPI_PO_CREATE, BAPI_PO_CREATE1, BAPI_PO_CHANGE, BAPI_PO_GETDETAIL, BAPI_PO_GETITEMS, BAPI_PO_GETITEMSREL, and BAPI_PO_GETRELINFO.
5. For more information on purchase orders, refer to the SAP library (under MM Purchasing -> Purchase Orders) or the Help for the Enjoy Purchase Order, or choose the path Tools -> ABAP Workbench -> Overview -> BAPI Explorer from the SAP menu.
regards
reena

What are the mandatory fields while creation of material master in differen

what are the mandatory fields while creation of material master in different views?

Hi Gopi,
This is purely depends on the function configuration, which would be done MM consultants. Kindly check with them.
thanks & regards
Kishore Kumar Maram

What are the mandatory fields needed to setup/register the SIP phone manually in CUCM

What are the mandatory fields needed to setup/register the SIP phone manually.Also, if someone can let me know the mandatory fields for Cisco based SIP phone and also the third party SIP hard phones like Avaya or any other Third party SIP phones both Soft phone and physical phone requirements...in CUCM
Please suggest...I need to know if MAC address is mandatory for all Cisco SIP phone to setup

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/7_1_2/ccmcfg/bccm-712-cm/b09sip3p.html
http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-version-70/112110-phone-add-00.html

What are the mandatory fields in DTW for opening balances imports?

Hi All,
As the title mentions could you please help by listing all the mandatory fields in DTW for importing opening balances ?
Thank you for your help,
MB

Hi Gordon and all,
I have a look at the SDk help files and almost cried but am i right in thinking it is Account Code, Debit and Credit fields that are the mandatory fields for opening balances?
These sdk help files are awful by the way...really awful.
MB

SCCM 2012 R2 ,which are the roles should be installed on CAS and which are the roles should be installed on Primary

Hi All
Which are the roles in SCCM 2012 R2 ,which cannot be installed on CAS and which are the roles which can only be installed on CAS . and which are the roles which should be installed on both CAS and Primary.

Here is the official list that describes where you can install the different roles:
http://technet.microsoft.com/en-us/library/gg712282.aspx#Plan_Where_to_Install_Sites
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

What are the Mandatory fields????

Hi.... Experts...
Please spend your valueble time for me.... I can get back to you with 10 points....
Here I got a requirement to create contract with VA41 transaction...
But I am in confusion with feilds which should be must record...
Please guide me on mandatory fields of VA41 transaction....
Thanks,
Naveen.I

Hi,
When ever you want to know the required fields for any transaction just try to run the Transaction In SHDB in forgroud mode with a recording name.
You will easily get to know the required fields to be entered for a given transaction.
Sometimes when we run this VA41, eventhough some fields are not mandatory we dont pass them but we willnt b able to create the document eventhough some fields are not mandatory to fill> To have the clear idea abt the manadotry fields try to run in SHDB.
for this VA41, ther mandatory fields are-
contract type (VBAK-AUART)
Sales Area is a combintaiotn of SAles Org, SAles divnsion, Distirbution channel hende all 3 are required to be filled.
1st screen-
Sales Area(VBAK-VKORG)
Division(VBAK-SPART)
D.Channel(VBAK-VTWEG),
2nd screen-
Customer code(kunnr),
Contract validity,
material code(matnr),
quantity
plant(werks).
Best Wishes,
Chandralekha
Edited by: Craig Cmehil on Jun 30, 2008 11:24 AM

What are the mandatory fields of BAPI for creating a new purchase order?

Hi friends,
I am very new to XI.My Boss has given me task to create a purchase order using BAPI. I want step by step guide to create it.How will i know which fields are mandatory for BAPI_PO_CREATE?

Hi Shweta,
However It depends upon the configuration that which fields to be passed.
But you can check this by running the BAPI in the SAP system by using transaction Se37.
The most commanly used fields are:
HEADER :
DOC_TYPE                       NB
CO_CODE                        9001
PURCH_ORG                    9001
PUR_GROUP                    900
VENDOR                         100000
ITEM
PO_ITEM                        00001
MATERIAL                      MM10
STORE_LOC                   01
MAT_GRP                       01
SHORT_TEXT                  SERVICE (optional )
PLANT                            9001
NET_PRICE                    500
ITEM_SCHEDULE
PO_ITEM                        00001
SERIAL_NO                      0001
DELIV_DATE                     05.04.2008
QUANTITY                                  1.000
You can run the BAPI with some test data... if something is missing the BAPI will ask for it... the Results are displayed in Return Table.
Regrads,
Sachin

RV_INVOICE_CREATE for this FM what are the mandatory fields

Hi guru,
        in my process development, first i am creating the sales order using the BAPI FM SD_SALESDOCUMENT_CREATE, From this FM i get the sales order no, after that i use this fm RV_INVOICE_CREATE , then i pass the VBELN (sales order no), but it is not created the invoice no,
what are the fields i have to pass for this FM.
What is the use of this FM : RV_INVOICE_DOCUMENT_ADD, is it useful in my scenario.
plz give the details briefly
thanks & regards
     raj.

HI ,
call function 'RV_INVOICE_CREATE'
    exporting
      with_posting = 'B'
      vbsk_i       = i_xvbsk
    importing
      vbsk_e       = i_xvbsk
    tables
      xkomv        = xkomv
      xvbpa        = xvbpa
      xvbrp        = xvbrp
      xvbrk        = xvbrk
      xkomfk       = i_komfk
      xthead       = xthead
      xvbfs        = i_vbfs
      xvbss        = i_vbss.
These table are not optional , these all are mand...
Reagrds,
Bharani

Which are the Key fields in the iTunes Music Database

I assume that the iTunes Music folder is really a database for all the music. I further assume that this database has a Key Field (1 or more) which are necessary for it to function.
Which fields are these and what are their names??
I am still hunting for the songs that are missing in iTunes but are in the library.

Ignore the question. I found the missing files. Had nothing to do with "key fields". Thanks

Problem with the hierarchial fields in a Purchase order xml report

Hi,
I am having a problem with the hierarchy problem. We are populating attribute 15 of a PO header. some times it can be null. FYI, we are using 11.5.10 instance where oracle supports direct PO template rather than having a rdf file.
And now in the xml report, if attribute15 of po header is not null then it is fine.
But if attribute15 is null, then the template is picking from the next available attribute15 that is from the po lines. As the line level group of "LINES" is between the "PO_DATA" (header group), hence the template is checking for next available attribute15.
Can any one please suggest how to design the template where we can make the template to check only for that tag at the header level group rather than the line level group tag?
Thank You in advance.
Regards,
Srinivas.

Hi
Incase you want to transfer attachements from SRM to R/3, then you try implementing the BADI in SRM side. The BADI which will help in this case is
BBP_CREATE_PO_BACK BADI.
Please read the standard SAP documentation of this BADI using SE18 Transaction, before making any code changes.
Few Important SAP OSS notes to refer in this case ->
Note 989184 - Transferred shopping cart with internal attachments
Note 550071 - FAQ: EBP - Shopping Cart
Note 916347 - Transfer shopping cart with internal attachments
Note 1001130 - FAQ - Attachment questions (Buyside)
Few useful links ->
http://help.sap.com/saphelp_srm50/helpdata/en/49/b32640632cea01e10000000a155106/frameset.htm
Re: Attachments to backend
Re: Document Attachments in Shopping Cart
Re: Attachment in SRM
Re: SRM Documents and Attachments
Re: Limit in Attachments of an item in Shopping Cart
Re: return delivery text from material document is not passed to SUS

Do let me know, incase you face any problems.
Regards
- Atul

Process chain creation and which are the module depending

Hi Expert,
I have confusion on process chain creation and triggering the process chain also same of the module are depending other module what those. What are thing we take consideration Please guide me in this regards .
Regards,
Ravi
Edited by: Ravichendra k on Oct 15, 2008 11:48 AM

Hi,
Here are a few links about process chains. Hope it helps.
http://help.sap.com/saphelp_nw04/Helpdata/EN/67/13843b74f7be0fe10000000a114084/content.htm
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=howtocreateaprocesschain&cat=sdn_all
http://sapbwneelam.blogspot.com/2007/09/how-to-start-process-chain-through.html
Regards,
Gaurav

Mandatory fields for mapping in ORDERS idoc.

Hi
I m working on File to idoc scenario for creation of sales order in ECC 6.0 , now I want to know what are the mandatory fields in ORDERS idoc which needs to be populated or else disbaled so that the sales order gets created properly in the ECC 6.0..
Pl let me know the method of finding mandatory field for mapping for any idoc and which fileds of idoc are to be disabled.
Pl help ..
ans will be rewarded .
thanks & rgds
mojib

HI,
U can disable the control record segment and in the IDOC adapter use the option apply control record from payload.
If you have set the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the following fields are filled from the IDoc-XML payload:
·        MESCOD
·        MESCFT
·        TEST
·        EXPRSS
·        STD
·        STDVRS
·        STDMES
·        SNDSAD
·        SNDLAD
·        RCVSAD
·        RCVLAD
·        REFINT
·        REFGRP
·        REFMES
·        STATUS
·        DIRECT
·        OUTMOD
·        CREDAT
·        CRETIM
read the information in below link:
http://help.sap.com/saphelp_nw70/helpdata/EN/ab/bdb13b00ae793be10000000a11402f/frameset.htm
thnx,
chirag

Vendor field on SRM Purchase Order

Hi.
Please can someone elaborate and explain why my preferred supplier that I have entered onto my Cart does not copy through to the Vendor field on SRM Purchase Order please? At this moment, the Preferred Vendor field is incorrectly populated whereas previously, only the Vendor field was populated. We have the ECS activated.
Thank you.
Pooja!

Hi
Prefered vendor - if you manually added a vendor - This partner function no. 39.
check your BBP_PD whether you have prefered vendor or fixed vendor in partner head.
Fixed vendor -partner function is 19 like contract ...etc
check these details or your approver might be changed your source of supply if he has access to modify the cart.
BR
Muthu

What are all the mandatory fields of the BAPI_PO_GETDETAIL?

Hi friends,
I am new to XI. I am using the "BAPI_PO_GETDETAIL1" in my scenario to get details of a particular Purchase Order. Can you tell me the mandatory fields of this BAPI?
Where should i look to identify the mandatory fields of a BAPI?
Thanks.
Senthil Nathan.

Hi you can see this in SE37 under the Import Tab. Here you see that the only mandatory input field is PURCHASEORDER. So if you provide the purchaseorder number you get alle the details for that.
Kind regards
Mikkel

What and Which are the Mandatory fields in a Purchase Order?

Similar Messages

Maybe you are looking for