Mandatory Field Vendor Classification - CT04

Hi,
I've created Vendor Characteristic thru CT04. How to ensure the field become mandatory field. It means that,
when user didnt enter values, the system will display "ERROR" message and force to enter value.
I can see the "Entry required" under CT04 tcode but it doesn't fully worked. It's only display "Info" message and user still able to leave the characteristic field with no value and save the vendor information.
How can it be done thru CT04 or is there any way it should be done in SPRO?
Your help much appreciated.

Hi,
1. I've done at CT04 - tick Entry Required. Characteristic name : for eg: VendorC
2. Run MK02. Enter vendor no.
3. Choose Enter. Vendor Details displayed.
4. Environment -> Classification
5. Enter Vendor Class. Click Enter.
6. Other Characteristic & VendorC characteristic displayed.
7. I've made some changes at other characteristic but not VendorC.
The Result, we still can save the changes without any error displayed. How we gonna give you the error details since there was not error display.
Thanks & Rgds

Similar Messages

Make Vendor Classification characteristics mandatory

All,
We have a vendor classification class and a characteristic. We have defined this characteristic as mandatory in transaction CT04. However when I create or change a vendor (transaction XK01/XK02) and go into classification I am still able to save the document without filling in reqired fields. I do get a popup saying that I haven't filled out the required field, but if I just press OK I'm still allowed to save even if some of the classifications mandatory characteristics are blank.
We really want users to be forced to fill in all required characteristics. Is there a way of doing this? There is a SAP Note - 661368 - BAdI for required entry field check in the classification. Even by making the fields mandatory in the BADI, we are able to go back to the prev screen.
I also tried implementing a user exit - EXIT_SAPLCLFM_002 (include ZXCLFU02). The pop up works, but we land up with some other issues like additional tabs coming on the screen or the SAP pop up coming up (resulting in 2 pop ups). So I am thinking is this may not be our solution.
Hope that you can give valuable responses to my issue above.
Thanks! Liz

Hi,
Try This by writing code in user exit SAPMF02K
sample code
IF I_MSEG-SOBKZ = 'E' AND I_MSEG-KZBWS IS INITIAL.
MESSAGE E002(ZSD01).
ENDIF.
Srikanth

Making Vendor Classification characteristics mandatory

All,
We have a vendor classification class and a characteristic. We have defined this characteristic as mandatory in transaction CT04. However when I create or change a vendor (transaction XK01/XK02) and go into classification I am still able to save the document without filling in reqired fields. I do get a popup saying that I haven't filled out the required field, but if I just press OK I'm still allowed to save even if some of the classifications mandatory characteristics are blank.
We really want users to be forced to fill in all required characteristics. Is there a way of doing this? There is a SAP Note - 661368 - BAdI for required entry field check in the classification. Even by making the fields mandatory in the BADI, we are able to go back to the prev screen.
I also tried implementing a user exit - EXIT_SAPLCLFM_002 (include ZXCLFU02). The pop up works, but we land up with some other issues like additional tabs coming on the screen or the SAP pop up coming up (resulting in 2 pop ups). So I am thinking is this may not be our solution.
Hope that you can give valuable responses to my issue above.
Thanks! Liz

Hi,
In the standard system you are always allowed to save the classification
even if it is uncomplete, you receive the warning message about the
required characters and if you save anyway, instead of preventing the
save it will change the status of the classification from '1' (Released)
to '3' (Incomplete). This is standard as the user should be allowed to
save the classification when incomplete and then come back later to
complete it at a more suitable time.
There is a userexit which you can use to change this functionality,
please review note 337262 which explains how to use this userexit
to prevent the save of incomplete classification.
Best regards,
Sandra

Mandatory fields to create vendor and PO

Hi all,
I am migrating data from legacy system to ECC and to SRM. I found mandatory fields in ECC and I am not sure what are the mandatory fields for SRM. I need for Vendor creation(Foreign vendors also) and open PO. Please reply.
Regards,
Balaji

Hi
Use the function module BBP_VENDOR_GET_NON_BAPI to create a vendor directly in SRM.
Function module - BBP_VENDOR_GET_NON_BAPI
Program - BBP_VENDOR_GET_DATA
BAPI - META_BUSINESS_PARTNER_CREATE
Also look at Function module - BBP_UPDATE_ATTRIBUTES.
Did you created any PO using that "bapi_poec_create"..? Don't forgot to add a commit work in your program.
You will have to develop your own XML mapping to create a PO in SRM.
You can use BAPI_POEC_CREATE (read SE37 documentation about GUIDs).
This one also uses internal functions BBP_PD_PO_CREATE, UPDATE & SAVE.
You don't have to take care of GUIDs. This function will generate them for you. You can pass the PO number as PO header GUID, and PO items as PO item GUIDs. This will make the links as well.
Please go through this as well ->
Re: Upload PO from XML file in SRM
Creating a PO with ME_CREATE_PO_ITEM
Re: Function Module/BAPI to create vendors in PPOMV_BBP
Re: BBP_PD_PO_CREATE
Create PO
Hope this will definitely help. Do let me know.
Regards
- Atul

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 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!!
P.S award the points.!!! !!!
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

PAN Number Field Mandatory in Vendor Master

Hi
We have created Account Group for Service Vendor and for this group we want to make PAN Number Field Mandatory . This Field appears in CIN Details Tab in Vendor Master .
In standard field selection I did not found that field . Please provide solution

Hi
I tried in my system and able to make PAN number as mandatory field.
see once u create the transaction variant ,kindly actiuvate the same by going to standard variants
one more thing until unless you go to the tab Withholding tax the system will not show as mandatory
Regards
Damu

Mandatory fields to replicate vendor from ECC to SRM

Hi all,
I created a vendor in ECC with all mandatory fields. But when I tried to replicate the vendors to SRM from ECC, I am getting errors like mandatory fields are missing. Can you please tell me what are the mandatory fields in SRM when we replicate vendors from ECC to SRM. Its Urgent.
Regards,
Balaji.S

Hi Balaji,
When you create Vendors properly in ECC it should not give such an error. You have to maintain basic data, Accounting data and purchasing data. Rest all are optional.
For replicating vendors from R/3 to SRM you should have a Vendor root org / group in SRM. BBPGETVD is used to replicate vendors to SRM by mentioning the logical system and Vendor Group ID.
Hope this makes you clear. Please explain the error clearly for further help.
Award points for helpful answers.
Rgds,
Teja

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 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

Mandatory Fields in iView created from SHD0 (sceen variant)

I am experiencing an issue with the Portal display of an (IAC) iView. The iView displays PZ05 and a transaction variant was setup to handle Emergency contact info. I created a screen variant for the second screen of this transaction (screen 0200) in which I made 7 of the fields mandatory in the variant. When this is tested on the R/3 side the mandatory fields are displayed the way they are supposed to be (with the check mark in the box, denoting it as a required field) however when they are displayed in the iView on the Portal the mandatory fields are completely filled up with the "check mark in the box". In other words the "Name" field is 40 character... and there are 52 "check marks in the box" characters filling up the field. The iView works great but this looks ugly. Any suggestions on what I should do to rectify the situation?
We are running Portal 6.0 SP15 with a stand alone ITS on a 4.6c backend and the Business Package is 50.4.

Hi Balaji,
When you create Vendors properly in ECC it should not give such an error. You have to maintain basic data, Accounting data and purchasing data. Rest all are optional.
For replicating vendors from R/3 to SRM you should have a Vendor root org / group in SRM. BBPGETVD is used to replicate vendors to SRM by mentioning the logical system and Vendor Group ID.
Hope this makes you clear. Please explain the error clearly for further help.
Award points for helpful answers.
Rgds,
Teja

Posting Vendor Classification Data using XK02 transaction

Hi All,
I am getting the vendor master legacy data by using an IDoc where in i am uploading the vendor information through transaction XK02. Now i have to enhance that to post the vendor classification information also. There is a function module IDOC_INPUT_CREDITOR, which is modified to a ZIDOC_INPUT_CREDITOR and the changes are made as per the client requirements. Could you please let me know how can i post the vendor classification information along with the vendor information. Let me know under which segment i need to write the code for this. Please share your experiences in loading the vendor master data load along with vendor classification.
Let me know if you need any more information.
Thank You,
Suresh

Here are the fields you need to fill.
BIKSSK-MAFID = 'O'.
BIKSSK-KLART = 'Z10'.
BIKSSK-OBJEK = 'YOUR-VENDOR-NUMBER-IN-INTERNAL-FORMAT'.
You may also need other values concatenated to vendor number if the classification is at company code level or purchasing org level.
BIKSSK-CLASS = 'YOUR-CLASS'.
I am not giving BIAUSP because I think you can figure it out.
Srinivas
Message was edited by: Srinivas Adavi

Vendor Classification Change Log Activate : Configuration Change

Hi,
I want to know what is the process of activate Change Log for the Vendor Classification. Please suggest.
Rgds

You can see in Xk02 / Xk03 transaction - Environment tab - Field changes..

Mandatory fields used in up dating vb60(vedor invoice) and ks01(cost centr)

Hi all,
can anyone plz send me the mandatory fields along with discription for recording vb60(vendor invoice) and KS01(cost centre).
ill award the points plz send me.

OTV Mandatory Fields - Bank Data

Hi there,
We would like to set Bank data as a mandatory field, when posting an invoice to a One Time Vendor, but cannot see how to make this mandatory. We can see where the Name and City are coded to be mandatory in FFCPDI (CPD_DATEN_PRUEFEN), but are not sure if this is where we should put the bank fields.
Does anyone have any suggestions, or another way to do this?
All replies welcome
Kind regards
Jackie

Hello,
When you create the vendor account group for customer.
Click on the Genral Data in this tab you make the bank details mandetory.
It will solve your problem
Regards
Ravi

Mandatory Field Vendor Classification - CT04

Similar Messages

Maybe you are looking for