Mandatory fields for VF01, ME51, XD01, Co40

can anyone tell me the mandatory fields for the tcodes to do BDC:
VF01
ME1
XD01
CO40

Hi,
ME51,VF01 -- No mandatory fields for these transactions.
XD01-- account group and customer number are mandatory.
CO40- Planned order mandatory.
Regards,
Jagadish.

Similar Messages

Mandatory fields for xd01

hai,
what are the mandatory fields to create the datas for xd01.(customer master data).
regards
surender

HI
MANDATORY FIELDS FOR CREATING CUSTOMER DATA ARE:
Account Group---ktokd(field name)
Name---Name1
Search term----sortl
postal code----pstlz
country-----land1.
Regards,
vineela

Mandatory fields for BAPI_ACC_DOCUMENT_POST

Hi
I am getting the follwing data from the file (Which is coming from oracle) invoice number and the amount,
from that i have to use Fb70 tcode for posting ,Please help me what are the mandatory fields for FB70,
how will get those fields from SAP. How to use the BAPI ?
Regards
Pabs

hi
check out this thread
Re: BAPI_ACC_DOCUMENT_POST
hope this helps
regards
Aakash Banga

Mandatory Fields for IDOC ORDERS01 for Pricing Condition EDI1 to trigger

Hi ,
I'm Testing an Inbound ORDRSP using we 19 for Pricing Conditions EDI1. What are the Mandatory Fields for IDOC ORDERS01
Thanks

hello,
I think it's better to execute VA01 to create a sales order; in that way you should have an idea of mandatory fields.
Thanks.

Can any one pls tell me the mandatory fields for BAPI_ACC_DOCUMENT_POST

hi all ,
Can any one pls tell me the mandatory fields for BAPI_ACC_DOCUMENT_POST
what all data i need to give to post a document.
Thanks and Regards
JK

Hi...
part of my source code:
** Header Data " Sending comp code
wa_documentheader-comp_code = 'XXXXX'.
wa_documentheader-doc_date = '20060620'.
wa_documentheader-pstng_date = '20060620'.
wa_documentheader-doc_type = 'XX'.
wa_documentheader-username = sy-uname.
wa_documentheader-ref_doc_no = 'XXxxxxxx'.
wa_documentheader-header_txt = 'Text Header.
wa_documentheader-bus_act = 'XXXX'.
*it_currencyamount
wa_currencyamount-itemno_acc = '1'.
wa_currencyamount-currency = 'COP'.
wa_currencyamount-amt_doccur = 1943.
APPEND wa_currencyamount TO it_currencyamount.
*it_accountpayable
wa_accountpayable-itemno_acc = '1'.
wa_accountpayable-gl_account = '1234567890'.
wa_accountpayable-bus_area = 'DIV'.
wa_accountpayable-item_text = 'Text 1 XXxxxxx '.
wa_accountpayable-pmnt_block = ''.
APPEND wa_accountpayable TO it_accountpayable.
*it_accountgl
wa_accountgl-itemno_acc = '2'.
wa_accountgl-gl_account = '1234567890'.
wa_accountgl-item_text = 'Text 2 XXxxxxx'.
wa_accountgl-bus_area = 'DIV'.
APPEND wa_accountgl TO it_accountgl.
wa_currencyamount-itemno_acc = '2'.
wa_currencyamount-currency = 'COP'.
wa_currencyamount-amt_doccur = ( 1943 ) * -1.
APPEND wa_currencyamount TO it_currencyamount.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_CHECK'
EXPORTING
    documentheader = wa_documentheader
TABLES
    accountgl      = it_accountgl
    accountpayable = it_accountpayable
    currencyamount = it_currencyamount
    return         = it_return.
clear it_return.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
      EXPORTING
        documentheader = wa_documentheader
      TABLES
        return         = it_return
        currencyamount = it_currencyamount "currencyamount
        accountpayable = it_accountpayable "accountpayable
        accountgl      = it_accountgl "accountgl
      EXCEPTIONS
        OTHERS         = 01.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

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

Mandatory fields for vendor master load

Hi Experts,
what are the mandatory fields for the vendor master upload? how can I find that?
Thanks for the help.

In addition, you can also refer the links:
http://www.auditnet.org/docs/SAPR3AccountsPayable.txt
http://users.ev1.net/~gmorris/securitydocs/SAPR3AccountsPayableMatrix.doc
Hope thisll give you idea!!
<b>P.S award the points.!!! !!!</b>
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

PS: Setting Project Profile as a mandatory field for Project Definition

Hi,
I would like to know how to set Project Profile as a mandatory field for Project Definition (CJ20N or CJ01). I tried to look for controls at OPUK config but the Project Profile is not available for definition - either mandatory, optional, suppressed, etc. Would appreciate if you can share your expertise on this.
Thanks!
Regards,
Vivian

Hi,
I would like to know how to include some additonal fields in OPUK/OPUJ. We have defined some .INCLUDE component / fields to SAP standard table PRPS/PROJ. We want those fields to also appear in OPUK/OPUJ so that we could also defined their characteristics - whether input, mandatory, suppressed, etc.
Thanks!
Regards,
Vivian

Mandatory Field for Entering Delayed Reason for project during scheduling .

Hi Friends
Here I have a question on "Scheduling"?
My Client want an mandatory field for entering the delay reason if any phase or tasks or project definition get delayed.
Your input would be highly appreciated
Regards,
YAGHAG

Hi Abhijit,
Thanks for your prompt reply.
I am implementing cprojects 4.5 in PLM 7.0 and not in PPM 5.0.
Regards

Mandatory field for TIN No, or Contact Person

HI Expert,
Can anyone please tell me code for Mandatory field for TIN number or Contact person at the time of adding Purchase Order.its possible by SP i tried for it but its variable so pls anyone have any idea.
Sudhir

Hi Sudhir,
Try This.
FOR Contact Person-----
IF EXISTS (SELECT DocEntry FROM [dbo].[OPOR]
WHERE
((CntctCode IS NULL OR CntctCode = '')
AND DocEntry = @list_of_cols_val_tab_del))
BEGIN
SELECT @error =1, @error_message = 'Your Error Msg1'
END
END
For TIN No.-------
IF (@object_type = '22' AND @transaction_type= 'A')
BEGIN
IF EXISTS (SELECT DocEntry FROM [dbo].[POR12]
WHERE
((TaxID11 IS NULL OR TaxID11 = '')
AND DocEntry = @list_of_cols_val_tab_del))
BEGIN
SELECT @error =1, @error_message = 'Your Error Msg 2'
END
END
Regards
Ashutosh T

Make material as a mandatory field for a particular document type in PR

Hi,
Currently we are in SAP 4.6c version. There is a business requirement for making material as a mandatory field for a particular document type of purchase requisition as they don't want the user to raise non material purchase requisition using that document type. The field for material is currently not available in the configuration for Define Screen Layout at Document Level for purchase requisition.
So could you kindly let me know the possible options to prevent user from raising a non material purchase requisition using that document type. If not could you kindly suggest me the user exits available at the time of saving purchase requisition which i could use so that we can write a code to check if the material number is entered or not. If not entered prevent the user from saving the purchase requisitions.
Also it would be helpful if you could let me know how the fields for enjoy transaction (like material,document type) can be made available for selection in the configuration for Defile Screen Layout at Document Level for purchase requisition.
All you help in the solving the above problem is highly appreciated.
Thanks & Regards
Ram

Hi,
Check below method works out for you, if you do not want to proceed with any ABAP development.
Have a custom field selection key with Material Description field as "Mandatory" and "Display" in Basic Data, Item selection group.
Assign this to your PR document type which need material as mandatory. With this you are making user to enter material indirectly as mandatory & user will not have an option of entering text which avoids indirect / service procurement.
"Material Group" option won't help as User can have default settings with some value and it updates even in display mode of field.
Regards,
Ram
Edited by: Ramprashanna S on Jan 11, 2012 11:51 PM

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

Mandatory Field for Master Data Creation

Dear Experts,
How can I make "Street 2" Field as a Mandatory Field when I create Customer Master data (XD01) ?
Thanks in advance for your kind support.
Best Regards.
Ripon

Hi
KIndly go to the belwo path and choose Create customer centrally and make the street field mandatory
SPROFinancial accounting-Accounts receivable and accounts payable -Customer accounts-Mastr data---Define screen layout per activity (customers)
By doing above system will show mandatory for all account group when creating customer master thjrough XD01
If you want to do mandatory for account groupo the n go to t code OBD2
Regards
Damu

Mandatory fields for delivery, GI BAPIs

Hi Folks,
scenario, i have an STO number for which i have to create an outbound delivery(like its done in VL10B). now that i have a delivery number, next i have to change the quantity of this delivery and post goods issue. after GI i need to post a GR. data is comming in from a non sap system.
bapis are -
BAPI_DELIVERYPROCESSING_EXEC
to create an outbound delivery
BAPI_OUTB_DELIVERY_CHANGE
to change the outbound delivery and then post GI
BAPI_GOODSMVT_CREATE
to creat GR
can anyone who has worked with the following bapis tell me what the mandatory fields are in each bapi. i am unable to post them. i would appreciate your help and thanks in advance.

Sample Code for BAPI_GOODSMVT_CREATE
Populate header data
Posting date
    x_goodsmvt_hdr-pstng_date = <deldate>.
Document date
    x_goodsmvt_hdr-doc_date   = <doc_date>.
User Name
    x_goodsmvt_hdr-pr_uname   = <ernam>.
User Name
    x_goodsmvt_hdr-ref_doc_no = <PO/Delivery No).
Bill of lading
      x_goodsmvt_hdr-bill_of_lading =<BOL>.
Populate item data
Purchase order number
    i_goodsmvt_item-po_number = ebeln.
Line item number
    i_goodsmvt_item-po_item   = ebelp.
Plant
    i_goodsmvt_item-plant     = werks.
Movement type
    i_goodsmvt_item-move_type =movtype.
Movement indicator
    i_goodsmvt_item-mvt_ind   = mvt_ind.
GR quantity
    if p_movtype = c_101.
      i_goodsmvt_item-entry_qnt = menge.
   else.
     i_goodsmvt_item-entry_qnt = menge * -1.
    endif.
GR UOM
    i_goodsmvt_item-entry_uom = meins.
Storage location
    i_goodsmvt_item-stge_loc = lgort.
Production date
    i_goodsmvt_item-prod_date = doc_date.
Delivery completion indicator
    i_goodsmvt_item-no_more_gr = c_x.
Movement Reason
    if p_movtype = c_122.
      i_goodsmvt_item-move_reas = c_12.
    endif.
endloop.
For each PO create a GR document
if not i_goodsmvt_item[] is initial.
    call function 'TRANSACTION_BEGIN'
         importing
              transaction_id = l_trans_id.
    call function 'BAPI_GOODSMVT_CREATE'
         exporting
              goodsmvt_header = x_goodsmvt_hdr
              goodsmvt_code    = x_mvt_code
         importing
              materialdocument = l_mat_doc
              matdocumentyear = l_mat_doc_year
         tables
              goodsmvt_item    = i_goodsmvt_item
              return           = i_bapireturn.
endif.

Mandatory fields for creation of FB60(vendor invoice),and FK01(cost center)

Hi all,
can u plz send me the mandatory fields(along with discription) for creation of FB60(vendor invoice),and FK01(cost center).
thank u,
Srinivas Reddy.

The FK01 is the transaction used to create a Vendor.
The mandatory fields are:
a. NAME1: For Name
b. SORT1: For CUIT number.
c. SORT2: For alternative CUIT number.
d. CITY1: For city.
e. STCD1: Tax Number.
f. Others depending the case.
For FB60 (Vendor invoice) the mandatory fields are:
a. ACCNT: Number of Vendor Account.
b. BLDAT: Date.
c. XBLNR: Reference Number.
d. WRBTR: Invoice Amount.
e. HKONT: G/L Account Number.
f. WRBTR: Invoice Amount. The same as d but in the item.
g.MWSKZ: Tax Type. Depending the case.
h. KOSTL: Cost Center. Depending the case but is highly probable that the field were mandatory.
i. Others. Depending the case.
I have given to you the most probably fields that are mandatory for those transactions.
Your Sincerely
Leonardo Lopez
FI Consultant

Mandatory fields for VF01, ME51, XD01, Co40

Similar Messages

Maybe you are looking for