About HR Inbound IDOC

Hi Gurus.
I'm new on IDOC subject.
I'm trying to test INBOUND HR IDOC.
I'm looking someone who tested or used on HR but i think it's not commom on that module.
I have on system an existing IDOC but everytime i try to test there is an error msg:
"Application document not posted" Number 51. It gives me something wrong with T777D table.
I appreciate if you could share your ideas and experience with me.
Regards.

Hi Mauricio
You may use PFAL transaction, to send data from one HR server to another.
Just give the object id and the receiver where you want to send the data, then login the receiver system
have a look on the idic using we02.
Or open tcode we02, give direction as 2(inbound), all idocs will be displayed, check the various parts of idoc over there
let me know issues if any
Regards
Manu

Similar Messages

Inbound IDOC commit

Dear all,
I need to clarify scneario below:
INBOUND process
Receive an Idoc, and inbound FM Z_TEST_IN will be executed. In inbound FM Z_TEST_IN, i have to update both Table ZHEADER and ZITEM. Since they are Header and item table, so if one of the table updating failed I've to perform rollback.
This is what i plan to do. Create 2 update task FM, one for ZHEADER update and one for ZITEM update. It will look like this:
Function Z_TEST_IN
CALL FUNCTION 'Z_UPDATE_HEADER'
IN UPDATE TASK
CALL FUNCTION 'Z_UPDATE_ITEM'
IN UPDATE TASK
ENDFUNCTION
My question would be:
1. Is there a system COMMIT WORK predefined in ALE layer? Or should i code an explicit COMMIT WORK in Inbound FM Z_TEST_IN?
2. Let's say update fail on one of the table, then ROLLBACK WORK will be triggered. So i'm aspecting data will not update to both tables, but how about the Inbound Idoc creation? Will the idoc still be created and shown in WE05?
Your comment is highly appreciated. Thanks in advance.

Hi,
1.You are using the Zfunction module,So you need to commit explicitly.
2.For standard ,implicitly done.
3.There is no need to create inbound IDoc.While processing only the Inbound idoc created.
4.Suppose if u want to create just go for We30.
5.We05 for just gives the list of idocs created.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Regards,
Shiva.

Ergent help about inbound IDoc for Goods Receipts

Dear friends
We have an ergent issue needing your help.
It is about DEVRY03.
Senarios is as following:
When we create a delivery by using VL31n, system try the IDoc and transfer to XI.
This is ok.After external warehouse system processes the IDoc,a message is sent back to SAP to post the goods receipts for the delivery.
Inbound IDoc type is DEVRY03. Is it right?
Which function module or which process ok is used for this senario?
Can anyone suggest how to do it?
Minghan

Hi !
Here comes some information for the INBOUND idocs....
There is a IDOC for transmitting goods movements from a legacy system.
It's message-type is: WMMBXY
IDOC-Type is: WMMBID02 (See we60 for it's pretty good docu....)
Prcoess-Code is :WMMB
The function that processes the data is: L_IDOC_INPUT_WMMBXY
Hope that helped a bit (for inbound)....
Regards
Rainer
Some points would be nice if that helped.

Payment Terms wrongly getting updated using Inbound Idoc

Hi All,
I have a inbound IDOC which creates new invoice evrery time it gets triggered. In the function module attached with that IDOC there is a logic written to fetch the payment terms from the vendor master LFB1. System should display that Payment terms in tcode MIR4 (Display Invoice) as per the logic written in the IDOC FM. But, It is displaying wrong payment terms.
Select single ZTERM
into v_zterm
from lfb1
where lifnr = p_lifnr.
I have checked while debugging my logic fetches the correct payment terms (20NM) but the same is not getting updated in MIR4 . wrong value (42 Net days ) geting updated. Please suggest what needs to be done to correct this.
Thanks,
VB

Vikas,
Your quesion can be bit more clear. What is that 42 days..?? To my guess based on your payment terms due date might be calculated and kept as 42 days. If you can tell us about 42 days then someone can help you.
Regards
Venkat

How to Test, Inbound idoc ,with out the Sender System, using a Text File

Hi Guru's .
we wanted to test BLAORD03 inbound idoc (Message Type BLAORD).with out the SENDER SYSTEM.
on the same client.
we wanted to test this idoc with text file from our local machine.
Can anyone give us detail steps.like how to create File layout
with Segment name,and values for the fields.how to pass this file to the system.
Thanks in advance.

Hi Aparna.
My requirement is to test the idoc with Inbound File.
Generate a file with the data entered through segments through we19 ,and use the same file for processing through we16.
when i am trying to do this syst complaing about
Partner Profile not available, and some times
port not available. and some times with
'No further processing defined'.
but i maintained part profiles and port perfectly.
Can you help me in testing with test 'File' port.

Inbound IDOC FM with BAPI

Hi Everyone,
I need some information about posting an application using inbound IDOC with BAPI. I need to write a FM for
Inbound IDOC with BAPI to post it. Can some one give me direction as where to start as I am new to BAPI.
Thanks in advance.
Regards,
vicky

Hi Vicky,
Please take a look at this link which will show step by step on how to setup inbound proscessing.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
Also check this links for sample codes.
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
Hope this will help.
Regards,
Ferry Lianto
Message was edited by: Ferry Lianto

Inbound idoc pordcr101 status 51 "enter purchase org"

in the we19 standard inbound for idoc pordcr101 i see the following
EDIDC with the partner/port info
E1PORDCR1
E1BPMEPOHEADER
    comp_code 300
    doc_type "NB"
    vendor 58121
    purch_ord 3000
    purch_group 000
E1BPMEPOHEADERX
    'X' next to respective fields
E1BPMEPOITEM
     po_item 00010
     Material scw1212
     Plant    3000
     qty       1000
E1BPMEPOITEMX
     'X' next to respective fields
Each time i run the inbound idoc pordcr101 in we19 with the above i get
enter purch org
i am really really stuck because i am entering purchase org but for some reason it does not know about it
what am i missing
HELP
I deleted the unused segments

no successful idocs in we19 up to this point
i was told
E1BPMEPOHEADERX 'X' next to respective fields this is used to indicate which fields are being input.
so i am using both
it is purch_org not purch_ord

How to cancel/reverse an inbound idoc?

I wish to cancel then reverse an inbound idoc specifically, WPUUMS01 (sales data compressed) as if the idoc never existed and wasn't processed in SAP.
The said idoc was already processed in SAP and the material and billing documents (in WPER) were already created.
Hope someone could help me on how to go about this.
Thanks!

hello ,
may be u can try to look in for the concerned bapi and then delet tht record via tht bapi for e.g say to delete a create sales order demo code is -
DATA: T_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
DATA: BAPISDH1X LIKE BAPISDH1X.
PARAMETERS: P_VBELN LIKE VBAK-VBELN.
SET THE DELETION FLAG
BAPISDH1X-UPDATEFLAG = 'D'.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
salesdocument = P_VBELN
order_header_inx = BAPISDH1X
tables
return = T_RETURN
COMMIT WORK.

Inbound Idoc to create SD invoice thru VF01

Hello All,
I was looking for an Idoc that allow me to create an SD invoice (and automatically then an FI posting) based on an SD order (as VF01).
I found some consultants talking about INVOIC, others about ACC_BILLING.
But after somes tests, none of the above works as expected. (-may be I am using a worng process code...)
Is there an Inbound Idoc where I can mention the same data as I will do in VF01 to generate an SD Invoice ?
Thank you All

There is no inbound IDoc, to my knowledge, and it'd be a very unusual scenario that would require invoicing through an IDoc interface. As soon as all the preceding transactions have been completed, not sure what sense it would make to wait for some kind of interface to give OK for the invoice creation...
Anyways, there is an option to run billing through a background job, which could be scheduled at regular intervals or based on an event. It'd be a very short program to get a document # and to trigger an event for the job or just run SDBILLDL directly, whichever is preferable.

Custom inbound Idoc error handling/ Workflow

Dear Experts,
I have a requirement where in I created a custom inbound idoc, but now i need to handle the errors in the workflow and notify the users thru workflow on an error.
Can some one please provide me a step by step guide on how to create a organizational unit, position and assign users to the position... and any other steps that need to be configured to notify the user on the error.
I'm pretty new to all these organizational uints and workflow related stuff. Any step by step would really be helpful.
Thanks for your time.
-Amit.
Moderator message: sorry, these forums cannot replace proper training, if there is step by step guides out there, then please use the search functions.
Edited by: Thomas Zloch on Oct 31, 2010 11:50 AM

Vittal,
1. If your requirement is for a SAP Standard Basic Message type and a Z extension: Then you simply have to find out the 'Standard Task' associated with basic type. You shouldn't worry about extensions. The standard task will be triggered at input error.
2. If your requirement is for a Z basic type i.e. you have created a customer IDOC for a custom processing: There are many dependencies on how you can achieve this. Firstly, you need to know how you're are processing this Z_IDOC. Are you using a standard FM or custom workflow or custom FM? There should be some triggering event within the processing of this Z_IDOC which will raise a certain flag when the error you want to capture happens (or when there is a generic error). You can configure this event in binding objects to trigger a workflow task. If you take a look at any standard tasks, you'll get an idea how the triggering event happens.
Once the workflow task (you can use custom task or use a standard task i.e. by triggering a standard event within the IDOC processing program) is triggered, you can either send it to SAP inbox, e-mail, trigger another processing etc. This is altogether another story.
So bottomline: For custom IDOC processing, you need to trigger an event when error happens. This can be a custom event or a standard event. This event should be linked to a task (custom/standard - check in SWETYPV). Bind all of these in PFTC. Once the task is triggered, you can do whatever you want to do with it.

Inbound/Outbound Delivery using DESADV01 Inbound IDOC

We are trying to use Message type DESADV, basic type DESADV01 to represent inbound and outbound material deliveries. Our SAP system is configured to accept these IDOCs and apply process code DESA which calls function module IDOC_INPUT_DESADV.
Our question is which of DESADV01's Segment-Field is used to tell the FM that we are talking about an Inbound or an Outbound delivery?
I have read something related to E1EDL21-LFART, but this field seems only present in basic type DELVRY01. Is there something similar in DESADV01?
Cheers

Thanks for your answer Anji.
We are not having problems with the direction of the IDOC. The IDOC is always Inbound to the SAP system, as we want it to be. However the delivery which the IDOC represents can be an inbound delivery (material has entered a certain plant) or an outbound delivery (material has come out of a certain plant).

Inbound Idocs: Queue Processing (non-stop queue?)

Hi everyone!
I have an issue with a File to Idoc interface. The customer would want the IDocs arriving to R3 to be in the same order they were sent from the legacy. From the File Adapter there isn't any problem using the EOIO QoS, and in the IDoc Receiver Adapter I checked the "Queue Processing".
There is something in the R3 side that the customer doesn't like much and it's about the stop of queue when an IDoc gets in error status: all the subsequent IDocs stay in status 75 ("IDoc received via qRFC").
I can change the status of the wrong IDoc and then release the stopped queue but: Is there a way to process serialized inbound IDocs avoiding the stop of the queue if an error occurs?
I'm using PI 7.0 SP30.
Thank you in advance!

First, this is not serialization, it's the queuing design EOIO... they are not the same.
So, since you activated EOIO in the Sender CC it's normal to have such behave (i.e. 75 status)...
Basically the serialization is not a good fit for these requirements.
Here is one solution:
1- Use dynamic queue name (via UDF) to create more parallelism since I dont think you have to queue all the IDOCs in one single queue.
2- Copy the IDOCs with 75 status to a new IDOCS with 64 (You must have very few)
3- Use RC1_IDOC_SET_STATUS to change the status of the IDOCS from 75 to something 73
4- There is standard report that you have to schedule and restart the queues
5- Reprocess the IDOCs from steps 2
The enemy of EOIO design is the user locks in the target system...
Cheers,
Fouad

Workitem is not generating for an Inbound Idoc

Hi All,
The problem I am facing, when inbound idoc is processing in SAP, if there are any errors occurred, it would generate a work item and that will be sent to user Inbox (SBWP) as per the workflow. Here it is not generating a work item for an inbound idoc where is there is an error. So user is not receiving work item mail to inbox, to check about the idoc error. This idoc has been processed through the function module.
Could you please let us know your input on this issue.

Hi Hitu,
The problem could be at multiple places.
To debug check the workflow which sends the workitem to the user when an error occurs.
Check if this workflow is getting triggered when the error occurs. If yes, then check the step whre this workflow fails.
Else, check the event linkage of this workflow and check if the associated event is getting triggered or not. If yes, check if the event linakge is active for the workflow.
There could be other places as well to diagnose the error.
Check if these inputs gives you some direction.
Regards,
Saumya

Inbound idoc ordsp fm:IDOC_OUTPUT_ORDRSP

my problem is that idoc fails when it comes in as a response of ORDCHG when user changes the delivery date in PO outbound idoc triggers with message type ORDCHG. Vendor sends the response as a confirmation of order via inbound idoc message type ORDRSP. it fails at that movement and gives an error ME 790(material number differ from .............) it is comparing the value of segment E1EDP19 qualifier 001 field IDTNR with ekpo-matnr &ekpo-ematn.
NOTE: there is value in segment and it is correct value. but when inbound idoc fails it is taking blank value in fekpo and comparing with ekpo-matnr &ekpo-ematn and giving an error ME 790
and when we reprocess the same failed idoc without any changes in it via WE19 it posted successfully
one more thing i noticed in all failed idoc that segment E1EDK02 qualifier 002 not got populated which contains vendor acknowledgement number.
but when we reprocess it in WE19 without doing any changes it posted sucessfully.
thanks in advance.

You say that "when we reprocess the same failed idoc without any changes in it via WE19 it posted successfully". What about if you reprocess the same iDoc via BD87 ? If you are using the same Function Module, this shouldn't happen, unless you have some very specific userexit code around the user or transaction type.
Cheers, Paul.

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

About HR Inbound IDOC

Similar Messages

Maybe you are looking for