Missing Mandatory field in IDOC

Hi All,
There is one outbound idoc which gives out an error status 40 "Application document not created in target system".
The error is Missing mandatory field : 1CS210,, not sure how tor find this missing field since the name does not match with the field names in the segments.
Can anyone help me?
Regards,
Anand

hi shiva,
pls try the below links you may get solution.
http://sap.ittoolbox.com/groups/technical-functional/sap-log-sd/mandatory-condition-mwst-is-missing-388959
Missing fields in Customer Master Data - 41k -
Re: Web Service - Error in Connection and Data fields missing - 44k -
http://blogs.ittoolbox.com/sap/ehadzipetros/archives/no-mystery-to-troubleshooting-gis-and-sap-always-begin-at-the-beginning-22646
www.helpsap.com/account1.html - 14k
thanks
karthik
reawrd me if helpfull

Similar Messages

Mandatory fields for IDOC

Do we need to specify the mandatory fields in IDOC as 1:Unbound? if its not then how does IDOC differentiate from Mandatory filed to non mandatory field if there has to occur a mapping error incase some mandatory field is missing.

Hi,
There is no need to modify the structure of an IDOC since it is already a standard. The mandatory fields are the fields that are needed (minimum) to be mapped so that the IDOC would post successfully But as for business requirements, you have to consult that with vendors.
Hope this helps,

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.

[SOLVED] AUR4 missing mandatory field: pkgver

This is the PKGBUILD
# Maintainer: AudioLinux <audiolinux AT fastmail DOT fm>
# Contributor: peace4all <markspost at rocketmail dot com>
pkgname=unified-remote-server
pkgrel=3
pkgdesc="Unified Remote Server"
arch=('i686' 'x86_64' 'armv6h')
url="http://www.unifiedremote.com/"
depends=('libxext' 'libx11' 'bluez-libs')
optdepends=('bluez' 'bluez-utils')
license=('freeware')
install=$pkgname.install
if test "$CARCH" == x86_64; then
pkgver=3.2.5.703
source=("http://www.unifiedremote.com/static/builds/server/linux-x64/703/urserver-$pkgver.deb" "urserver.service")
sha256sums=('5d02b48f9436815641718cef704592a11148f5894718d7a99f14da0fd0c52325' 'ca049fc2e6b08276bf22b262577feca3fb4f83bef95e8f95a95d16b8d59fd107' )
fi
if test "$CARCH" == armv6h; then
pkgver=3.2.5.452
source=("http://www.unifiedremote.com/static/builds/server/linux-rpi/452/urserver-$pkgver.deb" "urserver.service")
sha256sums=('4b5023b421d6323021350be5d74697b572cdc7faaf138fce49236c049b3016e0' 'ca049fc2e6b08276bf22b262577feca3fb4f83bef95e8f95a95d16b8d59fd107')
fi
if test "$CARCH" == i686; then
pkgver=3.2.5.648
source=("http://www.unifiedremote.com/static/builds/server/linux-x86/648/urserver-$pkgver.deb" "urserver.service")
sha256sums=('09843a8b03f849bc163bd28813719446e0d02eff32d1bfe3265f208b264ed46c' 'ca049fc2e6b08276bf22b262577feca3fb4f83bef95e8f95a95d16b8d59fd107')
fi
package() {
cd ${srcdir}
# decompress data
tar zxf data.tar.gz
# fix and revert desktop file to old behaviour
sed -i -e '9,24d;26d' $(find . -name 'urserver.desktop')
# install folders
mkdir -p ${pkgdir}/{opt,usr}
cp -r {opt,usr} "${pkgdir}/"
# clean up permissions
find "${pkgdir}" -type d | xargs -I {} chmod -R 755 "{}"
find "${pkgdir}" -type f | xargs -I {} chmod -R 644 "{}"
chmod 755 "${pkgdir}/opt/urserver/urserver"
chmod 755 "${pkgdir}/opt/urserver/urserver-start"
chmod 755 "${pkgdir}/opt/urserver/urserver-stop"
# add systemd service
install -Dm644 "urserver.service" "$pkgdir/usr/lib/systemd/system/urserver.service"
And this is the error when uploading:
[piero@archlinux unified-remote-server]$ git push origin master
Counting objects: 10, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (10/10), done.
Writing objects: 100% (10/10), 2.18 KiB | 0 bytes/s, done.
Total 10 (delta 2), reused 0 (delta 0)
remote: error: The following error occurred when parsing commit
remote: error: 1456b02848d6b941ba33e4e97697f7275acf5e4c:
remote: error: missing mandatory field: pkgver
remote: error: hook declined to update refs/heads/master
To ssh://[email protected]/unified-remote-server.git
! [remote rejected] master -> master (hook declined)
error: failed to push some refs to 'ssh://[email protected]/unified-remote-server.git'
If I change the PKGBUILD with pkgver out of if/test I have the same error...
Last edited by hifi25nl (2015-06-09 12:21:31)

I'm pretty sure AUR doesn't support packages that have different versions per architecture, I also wonder why the developer thinks this is a good idea. Anyway, as described here you should use source_$ARCH and sha256sums_$ARCH, not custom-if statements
Last edited by Spider.007 (2015-06-09 10:57:14)

FILE to IDOC SCENARIO NEED MANDATORY FIELDS IN MATMAS IDOC

Hi
I'm learning a scenario like File to Idoc which is i need some what are the mandatory fields for creting the message mapping.. between source file and MATMAS IDOC... because it was showing several fields.
is there any way to find out the fields we need to map compulsory... for sending IDOC successfully.
Thanks
Babu

Hi Babu !
Log into the R/3 system, transaction WE60, enter the idoc type MATMAS01 or 02, 03, 04, then press F8 or go to Documentation menu, HTML Format.
It will display a document, telling you which fields are optional and which mandatory.
Regards,
Matias
PS: please award points if helpful.

Missing fields in IDoc FIDCCP02

Hello Experts ,
I am using FIDCCP02 IDoc to create a customer invoice.My item level data contains a field XMWST (Calculate Tax) which i can not find anywhere in the IDoc.Even BSEG-ANFBN ,BSEG-ANFBU,BSEG-ANFBJ,BSEZ-EGMLD,BSEG-HZUON fields are not present in the IDoc.I am mapping the above fields using LSMW.Please let me know how to map the above also it would be helpful if these fields are named differently in the above IDoc.
Thanks and regards,
Vijay Simha CR
Moderator message : Duplicate post locked. Continue with the earlier post [Missing fields in IDoc FIDCCP02|Missing fields in IDoc FIDCCP02].
Edited by: Vinod Kumar on Aug 31, 2011 5:45 PM

Hello Shafiq,
Thanks for your comment. I think it's a good idea to deactivate option to send IDocs immediately and create an own job to trigger it regularly. It would be great if according user exits would be triggered also only when the IDoc job starts. Otherwise I would have to create a copy of RSNASTED and enhance it to fill according values. Depending on the outcome I'll reward your anwser. Nevertheless thank you very much until then.
Eddy

Value for mandatory field is missing

Hello again,
I created an application how descripted in 95 Implementing Remote Persistency with CAF and RFCs (Service).
The problem occurred when I try to search for an entry. I get the following error:
german: "ERROR. Wert für Pflichtattribut ... fehlt:"
english: "Value for mandatory field ... is missing"
The option mandatory=true seems to be the problem. But I need this option to make these fields available for the mapping with the create method. After I while of tinkling I find out that the errormessage appears when I set more than to fields to mandatory.
Do anybody know how to resolve this error?
Thanks!

Hi Martin,
I reported this issue to development and they said that this is "by design". Here is the recommendation.
1. set the "Mandatory" flag to false for each attribute that is not required by your external interface.
2. perform mappings for only the mandatory attributes in the create method.
3. perform mappings for mandatory and optional attributes in the update method. The update method allows you to map optional attributes.
4. At runtime, first call the create method with only the required attributes, then call the update method to fill any optional attributes.
This should eliminate the error that you get in the Service Browser.
Best Regards,
Austin.

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

Procedure to find mandatory field in an IDoc Segment

Hi all,
Please guide me to find mandatory field in an IDoc Segment.
Ex: I went to MATMAS05 IDoc type. I know that E1MARAM and E1MAKTM are the mandatory segments for MATMAS05 IDoc Type.
But, I would like to know what are the mandatory fields for E1MARAM or E1MAKTM segment.
Please guide me to find mandatory field in an IDoc Segment (for the above example).
Thanks,
Sudarsan

hi, here I have a good suggestion to solve your problem.
Assuem you are research which field is mandatory in your mastr data inbound. Let's suppost it's a material. You already known how to create it in online t-code, which field should be filled, which view should be inputed.
Then, configure you material related IDOC for outbound, make sure that system will send out a material IDOC to other partner system (it can be a dummy system)when you create it.
Then check the sent IDOC, you can find out how SAP system fill the IDOC according to your input.
You can get to know how to fill your IDOC in this way.

WLK1 Table mandatory field data for DATBI & DATAB missing

Hi ABAPers,
I have an issue in production i.e in table WLK1 few records have created which have data missing from mandatory field DATBI & DATAB . Can anyone tell me the reason for that and how to delete those records.
Thanks,
Soumya .

Here in our case we are creating materials and availing certain time period i.e. DATAB and DATBI for selling those in different stores. So if those goes missing will certainly cause problem.
So, just by a creating Z code for selcting those records then deleating them and after that listing them again to database will solve the problem or not?
Thanks.

How to identify mandatory fields while using an idoc

Hi
I am new to Idocs. I want to find out the mandatory fields in the segments that are used in an Idoc.
Please help.
Regards,
Lohitha

Hi Lohitha,
I dont think there is a straight forward/documented way of knowing a mandatory field within a segment, however you can use WE30 or WE60 to identify the mandatory segments in an IDOC.
I guess you will have to use common knowledge of the requirement to know/identify a field that might be mandatory. For Ex: when you are creating an ITEM on a SO, Material is mandatory etc
Regards,
Chen

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 fields error messages in HCM forms and processes

Hi,
This may sound to be a very simple problem but I am unable to get to the root of the issue and thus need an expert advise here.
I have created several forms in the system out of which one is an OM form using SAP_PD service for create position. There are few mandatory fields in the form scenario such as
TITLE
ABBREVIATION
EMPLOYEE GROUP
EMPLOYEE SUBGROUP
As expected, system issues an error message if these field are left out blank but the error message is generic for all the fields and is missing the field name.
Actual Error Message
Complete the required entry field ""
Expected Error Message
Complete the required entry field "Employee Group"
Complete the required entry field "Employee Subgroup"
However, there are couple of fields in the form scenario which issues a correct error message
Complete the required entry field "Object abbreviator" (P1000-SHORT)
I am unable to identify the difference between the couple of fields that issues a correct message and rest 20 other fields which doesn't.
Regards,
Murtuza Kharodawala

No, if I enter all the mandatory fields on the form then there is no problem. It allows me to move ahead and submit the form successfully.
As recommended by Siddharth, I tried debugging the message class and what I observed was it passes the complete_fieldname value as Personnel Subarea (I1008_BTRTL) and system expects it to be I1008-BTRTL.
SAP as a fallback tries to read description from the table T5ASRFSCNFLDT but it has a_form_scenario as blank and complete_fieldname has a concatenated value "Personnel Subarea (I1008_BTRTL)" instead of "I1008-BTRTL".
Not sure what am I missing which causes it to have this wrong error message.
Regards,
MK

Logical System field in BD10/BD14 need as a Mandatory Field

Hi All,
Good Day,
We have Logical System field in BD10 or BD14 etc.. TCodes and I would like to make this field as a Mandatory field. The reason for this is, while sending the Materials using BD10, and If I haven't enter any value for this field, IDOCs are getting generated and sending to all the logical systems say Dev, Quality and Production too. I want to avoid this.
So Is there anyway where we can make the filed "Logical System" as a mandatory field.
Thanks in Advance.
Param.

HI Param,
try BAPI_IDOC_INPUT1and check it in WE57 tcode.
hope this helps
regards
Aakash Banga

Any way to validate the Mandatory field in the XML file

Hi,
Is there any way to validate the Mandatory field in the XML file. I created an xml type table xml_validate based on the schema and insert the XML files with statement.
INSERT INTO xml_validate(warehouse_id,xml_file_name,warehouse_spec)
Values (agreementid,p_filename,XMLTYPE.createXML(l_clob));
It is validating the data types, extra tags etc but not validating the missing of the manadatory tag/value.
Thanks in advance
Rizly

Hi Ants,
Yes, I was not doing the strict validation, after searching the forum i understood that was the reason. So i did this way,
begin
for x in (select myColumn from myTable where WAREHOUSE_ID=41) loop
x.myColumn .schemaValidate();
end loop;
end;
The out put is:
ORA-31154: invalid XML document
ORA-19202: Error occurred in XML processing
LSX-00011: internal error: LsxvPushCandidate array overflow
ORA-06512: at "SYS.XMLTYPE", line 345
ORA-06512: at line 3
My i know more information about this error, especially
LSX-00011: internal error: LsxvPushCandidate array overflow
Thanks in advance
Rizly

Missing Mandatory field in IDOC

Similar Messages

Maybe you are looking for