Inbound IDOC basic type HRMD_A07: Why no validation available?
I am using a standard inbound IDOC basic type HRMD_A07 to update employee master data (IT0000 & IT0001). However, i found out that this IDOC just directly updates to the infotypes without any validation. For example, i provide an invalid company code (BUKRS) and personnel area (WERKS), the IDOC still updates into database without any proper validation.
Filled the following fields in the IDOC segments:
E1PLOGI
plvar=01, otype=P, objid=00000001, opera=I
E1PITYP
plvar=01, otype=P, objid=00000001, infty=0000, begda=20120101, endda=99991231
E1P0000
pernr=00000001, infty=0000, endda=99991231, begda=20120101, massn=01, massg=01, stat1=3, stat2=3
E1PITYP
plvar=01, otype=P, objid=00000001, infty=0001, begda=20120101, endda=99991231
E1P0001
pernr=00000001, infty=0001, endda=99991231, begda=20120101, bukrs=XXXX, werks=XXXX, persg=1, persk=EC, abkrs=99, plans=00000111, otype=S
Please help me out in case I am missing something. Thanks.
Additional Info:
In WE21 at the TRFC Port, it is possible to set this Option:
Send Only Fields of Selected Segment Version
The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
But if we are using an reduced message type, all fields of the newest release are in the segement.
The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
But it is never called when createing an material IDOC with BD10.
Bug or feature?
Kind regards
Manuel
Similar Messages
-
Status 51 in IDOC Basic type: ORDERS05
Hi,
When Inbound IDOCs of IDOC basic type : ORDERS05 are processed in bulk then few of the IDOCs go to status 51 with error message : "Sales organisation, Distribution channel and division cannot be determined for the customer (followed by customer number)". But when these failed IDOCs are processed again using BD87 few more IDOCs go to status 53. Similarly if the failed IDOCs are reprocessed for 4/5 times without changing any data in the IDOC then all the IDOCs go to status 53.
When I try to create a duplicate IDOC using WE19 then the IDOC goes directly to status 53. So if processed in bulk then few IDOCs go to status 51 and when processed one by one the IDOCs go to status 53 without any problem. Can someone tell me what is the reason behind it and what has to be done to avoid the continuous reprocessing of IDOC.Hi,
When Inbound IDOCs of IDOC basic type : ORDERS05 are processed in bulk then few of the IDOCs go to status 51 with error message : "Sales organisation, Distribution channel and division cannot be determined for the customer (followed by customer number)". But when these failed IDOCs are processed again using BD87 few more IDOCs go to status 53. Similarly if the failed IDOCs are reprocessed for 4/5 times without changing any data in the IDOC then all the IDOCs go to status 53.
When I try to create a duplicate IDOC using WE19 then the IDOC goes directly to status 53. So if processed in bulk then few IDOCs go to status 51 and when processed one by one the IDOCs go to status 53 without any problem. Can someone tell me what is the reason behind it and what has to be done to avoid the continuous reprocessing of IDOC. -
I can create material using inbound Idoc of type MATMAS01, but not MATMAS05
I can create material using inbound Idoc of type MATMAS01 in WE19, but MATMAS05 failed. In fact I used same data ( different material number), and same inbound function, but got different result.
What is different between MATMAS01 and MATMAS05? Is there some configuation need for MATMAS05?
My system is ECC5.0. Thanks.Hi, nagaraj
this is inbound IDoc, not outbound IDoc, so we can't assign Basic type in WE20, only can assign Message type.
In WE82, there are 5 records about Messagetype MATMAS:
Message type Basic type Release
MATMAS MATMAS01 30A
MATMAS MATMAS02 30D
MATMAS MATMAS03 40A
MATMAS MATMAS04 46C
MATMAS MATMAS05 470
I think it should be ok.
In WE57, there 2 records are exist:
FM_name BasicType MessageType
IDOC_INPUT_MATMAS01 MATMAS01 MATMAS
IDOC_INPUT_MATMAS01 MATMAS05 MATMAS
so I think all configurations should be ok.
Message was edited by:
liu bin -
How to change the default IDOC basic type from CREMAS05 to CREMAS04.
Hi All,
How to change the default IDOC basic type from CREMAS05 to CREMAS04 when sending Vendor Master Data.
When I generate partner profile, the system will add the latest version of IDOC type which is CREMAS05 to the Outbound message. In my project, I'm asked to use CREMAS04.
I want to use BD14 to send master data directly, but the program will generate IDOC using CREMAS05. Is there a way that I can change it to CREMAS04? And also for using Change Pointers, I want to use the report RBDMIDOC, but i have the same problem.
Thanks
Sai Krishnaexecute WE20 and edit the outbound parameters
here is a pretty good example: http://documentation.softwareag.com/webmethods/sapr3_gateway/sap231/pages/sapdist.htm
Edited by: Jürgen L. on Sep 7, 2011 9:49 PM -
Basic type :HRMD_A07 in which table data will be store
Hi,
I have the basic type HRMD_A07 .so can any one tell me in which table data will store .
Thanks in advance.
RegardHi,
Check the following link for more information on tables and the flow of information in sd
<u>http://www.erpgenie.com/sap/abap/tables_sd.htm</u>
Award points if it adds information.
Thanks
Mohan -
F110S - debugging - Idoc basic type PEXR2002
Hi,
i'm trying to debug F110S and its not stopping in FEDI0003 routines. am i missing something.
i have to populate bank details in this Idoc (basic type pexr2002 and message type PAYEXT)
please let me know.
Thanks.
Edited by: vij k on Aug 5, 2009 9:51 PMfigured it out. Thanks.
-
Processing IDOC Basic type ORDERS05 in CRM...
I'm processing (via WE19) an IDOC (Basic type ORDERS05) to create a Sales order withing CRM. I'm getting there in that a sales order is being raised, although there is no item level details so far. I know that config of the system plays a big hand in what fields within the IDOC need to be populated but has anyone actually posted/raised a Sales order in this way and can you tell me what fields within the IDOC are mandatory. Or perhaps suggest how I might derive this.
Ideally I wanted to extract a sales order and produce an outbound IDOC and then compare the contents, but I can't (don't know how) do this.
Any help would be greatly appreciated.Hi Garry,
Here is an order from WE19, which works
E1EDK01
ACTION: [QUAL] - suggesting 000 - no changes
E1EDK14
QUALF: [QUAL] - suggesting 008 - sales org
ORGID: [ORGANIZATION] - anything you have defined /your side/
E1EDK03
IDDAT: [QUAL] - suggesting 002 - delivery date
DATUM: [DATE] - any date
E1EDKA1
PARVW: [QUAL] - may use AG as 'sold to' here
PARTN: [PARTNER#] - any partner defined
E1EDKA1 - not necessary
PARVW: [QUAL] - may have different 'sold to' and 'ship to' or 'bill to'
PARTN: [PARTNER#]
E1EDP01
POSEX [ITEM#] - for example '1'
MENEE [Unit of measure] - PCE for peaces
E1EDP02
QUALF: [QUAL] - suggesting 001 - customer order
BELNR: [document number] - document #. any
E1EDP20
WMENG: [Scheduled quantity] - any - quantity
EDATU: [Date] - any - when to deliver
E1EDP19
QUALF: [QUAL] - for example 001 - used by customer, 004 - used by manufactured
IDTNR: [material ID] - material ID
E1EDS01
SUMME: [Total value of sum segment] - check for the number of lines in PO1.
Hope this helps and do not forget to allot points.
Regards,
Martin -
Hi all,
can any one take me the structure of Idoc Basic type PEXR2003.
WE60 ==> Basic Type checked ==> enter PEXR2003 ==> F9 key
Thanks in advance
Ragerds
MercuryxUp,
No ideas?????? -
Release? while assigning Z Message Type to a Standard SAP IDOC Basic type
Hi Experts,
Am trying to assign a custom Message Type to a Standard SAP IDOC Basic type in WE82 transaction, but am not sure How to find the Release(last column of WE82 Tx)? Pls. let me know.
Thank youHello,
In case of IDOC, Go to Transaction WE30, type your IDOC name & select basic type & extension.
After that select Go to -> Header data (Shift+F7), you will Idoc header info. In the same pop-up you will find IDOC release for which version.
Regards,
Sameer -
How can I delete the IDOC basic type and extension?
Hi,Expert:
There are some idoc basic types and extension which are not used any more in our system.Now we want to delete them.but when I delete them using tcode:WE30, system said that the basic type or extension has been released and they can not be deleted.
How should we do to delete these idoc types?
ThanksFrom the top menu > edit> cancel release then try to delete
a®s -
What is the IDOC Basic Type for sales order creation
Hi Experts,
Can anyone tell me Idoc Basic type for sales order creation.
Thanks
PrashantHi,
The basic types for creating the order are:
1.Orders01
2.Orders02
3.Orders03
4.Orders04
5.Orders05.
The basic type for SIS order is:
SISCSO01.
Regards,
Krishna. -
Inbound IDOC:Not able to create OBJID while testing basic type HRMD_A07
Hi Friends,
I am trying to test creation of organization data (HRP1000) for inbound idoc via tcode WE19 using basic idoc type HRMD_A07.I am using inbound fm IDOC_INPUT_HRMD.After test data entry,The idoc status is showing as 53 but in the database table HRP1000 objid is blank.It is not creating objid.can any body suggest solution for this.In this case,i want to create objid internally by the system.
Thanks,
Rajesh Kumar
Edited by: rajeshvatsa2005 on Feb 17, 2011 9:03 AMHi Rajanidhi,
Thank you for following up!
Perhaps optomizing the choice of forum for the questions could also help somewhat, in addition to following up on them. For example [this one|Forgot username & password; would have enjoyed more knowledgable attention in the NW Admin or Security forum.
Hope that helps in future,
Julius -
Inbound idoc mess type:DESADV basic type: DELVRY03 Item text
Hi all,
W're having a inbound process to create inbound deliveries via IDOC.
mess type:DESADV basic type: DELVRY03
We want to create a item text on the delivery via the IDOC. Is this possible?
I see that there's a segment E1TXTH9 - E1TXTP9 to put in texts.
But as I see it, to create a text, we have to give the delivery nr in TDOBJECT TDOBNAME TDID TDSPRAS LANGUA_ISO.
But since we are creating it, this is not possible.
Is there any way to create an item text on an inbound delivery via the IDOC? And how.
Thanks a lot!
Caroline,Hi Chris,
Before end of the ur functiond module (Idoc_input_xxxxxxx) create an Enhnacement spot . at this point I hope so delivey will be created already .so now u can get the delivery number
**********The Logic for Text Field filling*******************
IF NOT vbeln IS INITIAL.
DATA : L_FNAME TYPE THEAD-TDNAME,
L_FID TYPE THEAD-TDID,
IT_TLINE TYPE TABLE OF TLINE,
WA_TLINE LIKE LINE OF IT_TLINE.
CONSTANTS :C_FID TYPE THEAD-TDID VALUE '0004',
C_FID1 TYPE THEAD-TDID VALUE '0007',
c_Text(40) type c value 'xxxxxxxxx',
C_LANG TYPE THEAD-TDSPRAS value 'E',
C_FOBJECT TYPE THEAD-TDOBJECT VALUE 'BELEG',
C_FFORMAT TYPE TLINE-TDFORMAT VALUE '*'.
Reading the Idoc data table for Text field population
READ TABLE IDOC_dATA INTO IS_EDIDD
WITH KEY SEGNAM = c_segnam_e1edkt2.
MOVE IS_EDIDD-SDATA TO IS_E1EDKT2.
CONCATENATE mrm_RBKPV-BUKRS mrm_BELNR mrm_GJAHR INTO L_FNAME.
if sy-subrc = 0.
MOVE: IS_E1EDKT2-TDLINE TO WA_TLINE-TDLINE,
C_FFORMAT TO WA_TLINE-TDFORMAT.
APPEND WA_TLINE TO IT_TLINE.
CALL FUNCTION 'CREATE_TEXT'
EXPORTING
fid = c_FID
flanguage = C_LANG
fname = L_FNAME
fobject = C_FOBJECT
SAVE_DIRECT = C_X
FFORMAT = C_FFORMAT
tables
flines = IT_TLINE
EXCEPTIONS
NO_INIT = 1
NO_SAVE = 2
OTHERS = 3
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
I hope it resolves ur problem.Please let me know if u have any
Queries.
Rgds
Sree m -
IDOC Segement Release vs IDOC Basic Type
Hi there,
we are in an upgrade project and are runing into a general question about idoc creation.
Here is our behavior:
1. We have an reduced IDOC Type in BD53 ZMATMAS based on Messagetype MATMASDI.
2. It has 2 Segements E1MARAM with fields MSGFN MATNR PSTAT and Subsegemnt E1MAKTM with fields MSGFN SPRAS MAKTX.
3. Done the things around (RFC, Partner Profile, distribution model, changepointer ..)
4. In Distribution Model in outbound parameters, added our ZMATMAS.
As parameters we have: Partner type: LS, Message Type: ZMATMAS, Basic Type MATMAS03! and Seg. release in IDOC Type 46B. The Partnersystem is an NoneSAP System.
We are using MATMAS03 because this interface exists since 46B.
Now we send an Material with BD10 and Message Type ZMATMAS.
The Master and Commuidoc are successfull created. In BD87 the commuidoc is an MATMAS03 and has the expected 2 segements E1MARAM and E1MAKTM.
But what we do not expect, if we look into the content of E1MARAM there are ALL Fields which exist for the E1MARAM in release 7.00. Not only our 3 fields MSGFN MATNR PSTAT, or as we second expect only the segemnts that had existed in the segemnt E1MARAM in release 46B of MATMAS03.
The additional fields were filled with the NODATA sign.
My question is: Is it correct that an IDOC with basic type MATMAS03 can have an segement E1MARAM which is formated like the segemntdefinition E2MARAM007 (Release 7.00 / 6.03)?
The difference is definatly the length of the field! 876 in 7.0 vs 757 in 4.6A.
Why is SAP using the highest available segemnt release regardles which basic type we choose?
Isnt this wrong?
Additional infos:
We know that it is not possible to have an IDOC with basic type MATMAS03 with an segement e.g. E1MARA1 which only exists in newer basic type MATMADI if segemnt release is set to 46B in our distribution model.
Failure is: Segment E1MARA1 is unknown in Release 46B/ (correct and expected behavior)
If we are using this scenario with not an reduced message type, we will only find the fields in E1MARAM which are filled with data. (Not all fields of the latest release with nodata)
I traced the MASTER_IDOC_CREATE_MATMAS and hit the function IDOC_REDUCTION_FIELD_REDUCE. As you can see in it, it first checks if the idoc is an reduced message type, and at the end, fills up all fields with the "empty_symbol" which have no data in it. Why is this only happening if it is an reduced message type?
Kind regards
ManuelAdditional Info:
In WE21 at the TRFC Port, it is possible to set this Option:
Send Only Fields of Selected Segment Version
The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
But if we are using an reduced message type, all fields of the newest release are in the segement.
The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
But it is never called when createing an material IDOC with BD10.
Bug or feature?
Kind regards
Manuel -
IDoc basic type FIDCCH01 with error F5866
Iu2019m trying to create an iDoc with basic type FIDCCH01 and message type FIDCCH type. Iu2019m getting error F5866 u201CWhen calling up the interface to financial accounting, no entry was made in the transfer parameter "Application key" when I process the idoc. I do not see an idoc value by this name. What am I missing in my config?
Thanks,
StanStan,
First, I'd like to mention that you determine where the error message F5866 is used by entering this message in transaction SE91 and pressing the where-used function. This won't show you any of the dynamic message calls, but it does indicate that function modules FI_DOCUMENT_CHANGE and FI_DOCUMENT_CHECK_CHANGE are both possible origins for the message you received. These function modules are part of the FI Interface which I am assuming is called during the processing of your IDoc.
ACCHD-AWREF is one of the values passed to the FI Interface function modules, and message F5866 is returned when that field is blank. This is why I assume that the IDoc in question is missing a value for the AWREF field.
Based on that assumption, I checked the definition for the IDoc type that you mentioned, FIDCCH01, via area menu WEDI. This IDoc type contains a segment E1FIREF with field AWREF. You can use transaction WE02 to display the IDoc causing the error and check to see if the actual data for E1FIREF-AWREF is blank (ultimately leading to the blank ACCHD-AWREF value and error F5866).
Cheers,
Jamie
Maybe you are looking for
-
My iMac (late 2010 model) desktop's hard drive is fried (was about 200GB). How much am I expecting to pay for a new one and retrieve my information?
-
Hi , I have to add the condition type in the report V_NL. I want that condition type should populate in net price list (V_nl) But this is not reflecting in the report.How can I add it? Thanks in advance.
-
Renaming Folder... sigh
Hi all, Why would I not all of a sudden be able to rename a new folder? When I create a new folder, if I don't rename it right away while it's still selected, I can't rename it later, even in the Get Info box. I thought maybe it was my keyboard, unti
-
No more tech support link for iTunes?
I'm having a problem with my iTunes library. I tried to email tech support, but Apple has chosen to send you on a closed loop trying to find a working link. It was real straight forward before with an obvious link. Now how do you contact iTunes tech
-
Artists unchecked in Music sync still remain on iPhone?
I just recently switched from Sync "Entire Music Library" to "Selected playlists, artists, and genres". There's just some music I don't need on my iPhone that I want to remain in iTunes at home. Unchecking the artists/genres I don't want moved to the