IDOC structure for HRMD_A07

Dear All,
We want to create IDOC HRMD_A07 through SAP PI in ECC to create employee.
Please guide how we can get the output structure like
e1plogi
e1pityp
e1p0000
e1pityp
e1p0001
e1pityp
e1p0002
Whereas the standard IDOC structure is like as follows:
e1plogi
e1pityp
e1p0000
e1p0001
e1p0002
Reg,
NJ

Well, u can still create IDoc with the required structure. Thre is a test tool (tcode WE19) where u can create and populte the segments as u want for testing. Use the 'Create' button and place it in proper hierarchy.

Similar Messages

IDOC structure for shipment document

Dear All,
I need to know the IDOC structure to use for shipment document which will be updated with the actual shipment start end end times.(for carrier stop confirmation update interface.)
Please let me knnow.
Thanks in Advance.
KCR

Hi KCR,
Check the Message Type SHPMNT for IDOC types SHPMNT01,02,03,04,05.
Thanks & Regards,
YJR.

IDoc extension for HRMD_A07 - Error message B1-070

I am trying to create a custom extension to HRMD_A07 to capture some additional data added to infotype 0001. I have gone through the WE31, WE30, WE82, SM30 transactions to create the extension but when I try to test with PFAL I am getting the message B1-070.
Internal error: Program read table idoc_structure, command
data_select_for_block, argument ZHR_SEG
The extractor appears to be trying to fill in the original HRMD_A07 basic type and the HRMD_A07 with the extension.
Any hints?
Thanks, Rob.

Dear Rob,
Although your post's date is old but I would share my knowledge for whom has the same issue.
Last day I had the same problem and could not find any solution on internet so I had to trace the code. Fortunately I managed to fix the problem My colleagues had extended an IDOC by a segment but after that the segment was deleted so I was getting an error in ALE.
Issue comes "DATA_SELECT_FOR_BLOCK" method which is using I_DOC_DATA table that fills in PFAL transaction. thru running PFAL IDOC data reads from table T777D.
Go into and find the related record and clear it
By the way after that I found http://scn.sap.com/thread/3322338 useful
Cheers,
Omid

Download IDOC structure from SAP web Site

HI
to anticipate the SAP ERp upgrade, i would like to download the most up to date Idoc structure (for ADRMAS and DEBMAS) . Instead of download this structure from an SAP Instance , i would like to download it from SAP Web site.
Does anybody already do that ?
How can i proceed
regards
fred

Hi Siva
Thanks for your input. I Know and i did that from a couple of years , neverthelss, each time you upgarde your system, you have to rewrite your development. My goal is to try to anticipate that by for exemple download the IDOC structure in advance . Let me say IDOC structure used by MySAP ERp 2007 instaed of SAP ERP 4.6. If i can download those STructure i will not be obliged to rewrite my Dev after each upgrade. Do you see what i mean ?
regards
fred

Source of xslt mapping and XSD/ XMT target structures for standard Idocs

Hi,
I am working on R/3 - XI - ICH scenario. I need xslt mapping and XSD/ XML target structures for standard IDoc like PROACT01,DELFOR01, DELVRY03. I tried to search it on marketplace but couldn't find it there. As per configuration document, these things are shipped with XI mapping content in live cache CD. But I don't have this CD with me. Can anybody tell me the source for these target structures and mapping program. ( Please share marketplace, site link or send me across the mail [email protected])
Thank you in advance.
Anand More.

Anand the other option is to import the corresponding idocs into your integration repository and then you can view the generated XSD there.
As regards XSLT mapping, you need to basically first identify as to what form you want to transform your source idoc into.
For some help on XSLT mapping check the following threads,
https://www.sdn.sap.com/sdn/collaboration.sdn?contenttype=url&content=https%3A//forums.sdn.sap.com/topusers.jspa%3FforumID%3D44
https://www.sdn.sap.com/sdn/collaboration.sdn?node=linkFnode1-6&contenttype=url&content=https://Process Integration (PI) & SOA Middleware
Also have a look at my code samples,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-code-samples/generic xslt mapping in sap xi, part i.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9692eb84-0601-0010-5ca0-923b4fb8674a
cheers
Sameer

Generating IDoc DDF structures for EDI mapping

Hello all,
I am looking for a way to generate IDoc DDF structures to use them in the EDI mapping in Gentran.
I was able to find one on ERPGenie.com (developed by Kevin Wilson) but it is only available for ECC 4.x. We are on ECC 6 and the program gives me an ABAP dump when I try to run it.
Does anyone have the fix for this code? Or perhaps another way to accomplish this task?
Actually, I am only interested in generating the MBGMCR02 IDoc
Thanks for your help
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Apr 7, 2008 12:36 PM

It's been a long time since I have done any IDOC processing.
Go to SE37 and enter the function module IDOC_INPUT_ORDERS. Display the source code. Search for "CALL CUSTOMER". You should see several "CALL CUSTOMER-FUNCTION" lines. These are enhancements where you can manipulate the IDOC data. If you locate the correct one (where the data is read from the IDOC but not yet validated), you should be able to map the partner function value. Double-clicking on the number in quotes will bring you to an "EXIT_" function module. A "ZX" INCLUDE program is referenced. If you haven't used the exit yet, double-clicking on the ZX INCLUDE will create it. The values passed into the function module are available in the INCLUDE.
Ideally, you should create a project in transaction CMOD that references the chosen enhancement. This way you can activate/deactivate without commenting/uncommenting the code in the INCLUDE.

The XI does not send messages with correct IDOC structure

SAP XI 3.0 sends to ECC IDOC HRMD_A07
The XI does not send messages with correct IDOC structure.
In XI Design, Software Component RHEVOLU, Ive imported the Objects
HRMD_A.HRMD_A07 from SAP ECC; In Tools -> Export Reduced XSD, I saved
HRMD_A.HRMD_A07.xsd in Namespace http://suezambiental.com.br/HR . At
Message Mapping -> mmAdmissao, in Imported Message -> Import XML or
XSD, I imported the reduced Idoc file generated above, mapping source
fields to target fields.
The IDOC sent from XI to ECC has this structure (template: 22122)
E1PLOGI
E1PORIG
E1PITYP
E1P0000
E1P0001
E1P0002
Status 53 -HR: ALE inbound processing for HR master data
But does not update HR Master data.
The structure expected in ECC side (template: 20376) is:
E1PLOGI
E1PORIG
E1PITYP
E1P0000
E1PITYP
E1P0001
E1PITYP
E1P0002
Status 53 -HR: ALE inbound processing for HR master data
By using WE19 transaction, this structure was changed manually; so, the
HR Master data was updated.
Witch kind of customizing or correction could be made in XI, to send
the correct structure to ECC?
Best Regards
Claudio

Hi Claudio,
In your case, there are perhaps two causes:
1. perhaps when you have import the idoc, for a strange reason, a bad metadata was created by XI. You can clean this one in tcode IDX2 (Idoc metadata cache).
2. but it's also probably an error in your Message Mapping. Have you correctly manage segment E1PITYP?
Regards
Mickael

IDOC structure in F4 Help

Hey Guys
I m developing a search functionality where i need to search the message payload based upon a certain value in IDOC(it could be IDOC number,IDOC type,creation date etc etc).
My functionality needs complete Xpath for this search(for e.g. IDOC/EDI_DC40/DOCNUM) to be typed in manually.
Is it possible to provide IDOC structure in F4 help so that we can select the IDOC segment instead of typing it down?
Thanx
Saif

Hi Saif,
go to t-code we31--> press f1 and see the technical setting see the F4 help attached to it ..
use the same f4 help for the screen field you developed for custom Program..
For Segment F4 help...
Table Name        EDISEGMENT
Field Name        SEGTYP
for Idoc Number F4 help..
Table Name        EDIDC
Field Name        DOCNUM
for Creation Date F4 help..
Table Name        EDIDC
Field Name        UPDDAT
Regards,
Prabhudas
Edited by: Prabhu Das on May 12, 2009 12:04 AM

Idoc Structure From Flat FIle

Hi,
I have two queries.
1.I need to import idoc structure from excel file not from sap, is it possible ?
2 what are the detalied steps to implement following SAP note for getting processed file name at runtime.
Thanks & Regards
Tuhin
Symptom
You want to access the name of a file sent through a File Adapter Sender channel from a custom developed XI module.
Other terms
XI 3.0, XI30, File Adapter, Module Processor, Module Development, Modules
Reason and Prerequisites
The functionality described in this note requires SP 9 or higher of the component XI ADAPTER FRAMEWORK CORE 3.0.
Solution
The File Adapter passes the name of the processed file to the module processor. This information is available in a Hashtable object accessible as as supplemental module data under the name "module.parameters" within the module's 'process' method.
For further information, please take a look at the example code below:
public ModuleData process(ModuleContext mc, ModuleData md) throws
ModuleException
Hashtable mp = (Hashtable)
 md.getSupplementalData("module.parameters");
String fileName = null;
if (mp != null)
 fileName = (String) mp.get("FileName");

Hi Tuhin,

1. .I need to import idoc structure from excel file not from sap, is it possible ?
Yes and No; If the structure in the Excel sheet is defined in XSD format (XML schema) then it should be possible to import it assuming you are using XI 3.0. In 2.0 this is not possible.
Not sure if in XI 3.0 you are allowed to import Excel files straight forward into XI.
2 what are the detalied steps to implement following SAP note for getting processed file name at runtime.
I'm not quite sure but this looks to me like you have to implement this within a Java custom function/mapping...
The data (in this case the filename) is encapsulated in a Hashtable object available during runtime.
Cheers,
Rob.

Get Idoc structure and contents from Shipment Number

Hi all,
We have a 3rd Party Logistics company who wants to send us back minimal shipment data to enable us to update our shipment details. They want to send us the shipment number, and vehicle information. My tests (and SAP's documentation) have indicated that in order to modify a shipment via the message type SHPADV, you need to have the complete Shipment Idoc structure filled in in order for the idoc to process successfully.
My client has indicated that they want to use IDoc processing to manage the shipment updates.
Does anyone know of a FM that can be used to fill the shipment Idoc structures if only a shipment number is filled in? Or do the structures have to be modified manually? For example, these is a function called 'IDOC_READ_COMPLETELY' which populates all the segment details if an Idoc number is entered. I want something similar, but for a document number, in this instance, a shipment number.
Cheers,
Steve

Roger,
Thanks for this suggestion. I chose to go down another path which I put up here for those who have this problem in the future.
I have passed the shipment number and just the fields that require modification into user exit EXIT_SAPLV55K_020, and recorded the passed in values into variables.
I then executed the idoc_output_shpmnt idoc, which, when the shipment number is passed in to the nast-objky field, reads the required shipment data and populates the idoc_data table with the segment details as per sending the document out. But the FM doesn't actually call the ALE layer, so I then loop through the idoc_data table, modifying the fields that need to change with the values I've saved in the variables, and passed the modified idoc_data tables back into the idoc_input_shpmnt FM. Worked a treat.
Cheers,
Steve

File-to-IDoc, but the file structure is equal to the IDoc structure

hi,
we have a scenario where the incoming message has to be picked up by FTP. The incoming message is a flat file, no delimiters, no separators, nothing, however is exactly the IDoc structure.
Since the file adapter does not know how the structure is set up, because no tags are present, it can not translate the filestructure into any format. Therefore it can not be processed further.
Is there a way for a fileadapter to convert this plain file to an IDoc format, or to call the file-to-IDocadapter up front, the same way as if you would use in SAP the fileport in IDoc processing ??
thanks!

Hi Alexander,
XI understands ONLY XML. All messages to and from XI are always XML messages.
Now, if the file being placed by your Legacy System is not going to be an XML file, then you can use the content conversion of your sender File adapter to convert this non XML file to an XML file.
Same way, if the file that is required by your 3rd party application should not be in a XML format, you can use content conversion of the receiver adapter to convert XML to text and so on.
Basic point, all messages that reach the inegration engine of XI need to be in XML format and so you need content conversion to conevrt non xml to xml and vice versa.
To make note mapping cannot be performed with a flat file as XI understands only XML. Hence content conversion required.
Please go thru these links for step by step procedure to do the same:
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
http://help.sap.com/saphelp_erp2005/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
I hope I have answered your query.
Regards,
Abhy

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

Error when importing IDOC structure from SAP - Control record missing

Hi!
We are hitting problems when importing IDOCs from SAP into the Integration Builder. The import ends successfully but when we drill into the IDOC structure we get a message: Schema for type EDI_DC40.ASN_OUT.DELVRY01.Z1DELVRY (category Data Type) not found. This is only happening for one specific IDOC type only. We have checked all we can think of but cannot get this to work. Any help would be very much appreciated. Of course, points awarded for any good ideas. Thx, Duncan

Hi Duncan,
Taka a look at these threads which address similar issues:
Error during import of FIPARQ01 Idoc
Error during IDoc Import
Importing idocs:
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/78/21753251ce11d189570000e829fbbd/content.htm
Hope these help!.
Cheers,
Chandra
Message was edited by: chandravadhana gopalakrishnan

Idoc structure not displying in XPATH at Receiver Determination..!!! Urgent

Hi All,
Doing Idoc to File Scenerio,
In the receiver determination, I need to select the XPATH from the Idoc structure and by based on the GLN number which is coming in one of the segment, I need to pass to different receivers.
Problem here is Iam not able to see the Idoc structure in the XPATH to provide the condition.
But when doing File to Idoc scenarios, Iam able to see the File structure.
Any idea why IDoc structure is not displaying over here??
Its a bit urgent for me..
Waiting for your replys.
Thanks&Regards
Seema.

Hi,
This will help you now
Hi,
If you get the following msg while selecting the BS in Receiver Determination and if you are unable to view the Structure of the Source
"Message interface does not exist in any software components installed on this business system"
1) Open ID-----Double click on Business system that which u are using in the scenario
2) Check whether you are able to see the SWC in the Othere attributes TAB
3) If it is not there means goto SLD----Open the Technical System of R/3 by choosing Web as ABAp type
4) Click on Installed Products TAB
5) Click on Add New product and add your Product of the SWC whcih you are using for developement and Save it
6) Then goto Business systems TAB in the same Technical systems window and click on the Business System appears in the window.
7) Click on Installed products and Check the check box of your Product and then finally save that.
Now you should be able to see the SWC in the Othere attributes TAB in ID
Regards
Seshagiri

File to IDOC Scenario: where to import the idoc structure?

Dear all,
I have a short organizational question for you all. I have created a scenario where the MDM server places a file in a FTP directory and XI will take it from there for processing to IDOC towards the SAP system.
During design time I need to import the IDOC structure as the inbound interface for the SAP system.
My question in this situation is: do I import the IDOC into the namespace of the MDM (in which I keep the outbound interface and the mappings) server or do I place it in the namespace of the SAP system?
I ask this because in the latter case the IDOC structure will be the only object in the SAP namespace. If I do not do this, I don't have to create this.
What is the right thing to do from an organizational point of view?
Thanks in advance for your input.

Hi Yomesh and Sudheer,
thanks for your answers. To conclude this topic I will demonstrate how I have understood this all by giving you a short overview of how I will proceed now. Could you please comment???
Sender system is a SAP MDM system. For which I will create a SWC called <Company name>_MDM_DEV version 1.0.
For the receiving SAP Enterprise system I will create an additional SWC called <Company name>_SAP_DEV version 1.0.
And thus I do not put any objects under SWCs from the original installed product components.
Then I create a SWC for common objects as IDOCs (to what product does that need to be assigned???)
Then I will put the interface and message types in the corresponding SWCs and put the mappings in the source SWC as our landscape is not that huge.
How's that???
So under which product to create the SWC for common objects is my final question...
I will provide points to you both.
Cheers,
Auke
Message was edited by:
A. Schotanus

IDOC structure for HRMD_A07

Similar Messages

Maybe you are looking for