Inbound Idoc - permitted agents

In my inbound IDOC my partner profile permitted agents do not get a work item when the IDOC does not post due to some error. I seem to recall that some work needed to be done with the organization structure. Can you point me in the right direction as to which steps I may have missed?
Thanks

Hi Raynald,
Next step is to check with transaction SWETYPV if the type linkage for IDOCAPPL and event INPUTERROROCCURRED has been activated.
If this is the case you will find workitems for this task in the monitor (use transaction SWI2_FREQ) whenever an IDoc with status 51 has arrived for your message type.
Could you please check is the type linkage is active and if so wether or not work items have been created?
Regards,
John.

Similar Messages

Permitted agent in we20 - file-to-idoc scenario

Hello! I'm trying to make file-to-idoc scenario. Could you explain me, what should I enter in Permitted agent field?

Hi,
as per the documentation (F1 on the field):
Specifies the job (person or group of people) to be notified if processing errors occur on the IDoc interface
If an error occurs, only one (the most specific) job is notified. If an error occurs in the ORDERS message for partner HUGH, the system first attempts to determine whether a job responsible for ORDERS and HUGH is defined. If this is not the case, the job defined for HUGH (required entry) is notified.
The IDoc administrator is notified if HUGH does not exist at all in the partner profiles.
Examples
If the recipient type is 'US' ('user'), enter the name of the SAP user who is to be notified.
If the recipient type is 'O' ('organizational unit'), enter the organizational unit whose personnel is to be notified.
Regards,
Sergio

Workflow for inbound idoc failures

Hi Gurus,
Can anybody please point me to a place where i can start to see how i can setup workflow to notify users via SBWP whenver there is an inbound idoc error happens. We want to derive the standard functionality to its fullest even before thinking of putting any custom code. I'm specifically looking for hte order acknowledgemetns and shiipping notifications errors of idocs coming from the vendor
Thanks
anusha
Edited by: anusha vemulapati on Jul 2, 2011 4:43 PM

Hi Anusha,
The simplest way is to link the partner profile to a specific user ID. This is done in trs WE20 - you have the link to the WF recipient both generally for the partner (on the initial screen of WE20 when the partner has been selected) and specifically for the different message types - double-click on the inbound message type and choose the tab "Post processing - permitted agent".
You link the partner profile to a specific user by choosing the user type = "US" (user") and then specifying the user name below it. If you want several users to receive the same WF, you can link the partner profile to another user type, e.g. O = Organisational unit. Then you link the users to the organisational unit in trs PPOME.
As far as I remember, the WF for IDoc's in error is activated in the standard system, i.e. the setting above shall be sufficient.
BR
Raf

Inbound Idoc error notification

I created IDoc interfaces for FI, PO, and GR. As permitted agent, I specified a specific user for testing in partner profile. I want to widen the range of permitted agents, so I created a basic org structure (i.e: CoName->EDI Admin, EDI Support). I've assigned a few users to each position. This is where I get fuzzy about next step. Here's my understanding of next step
-> Assign tasks to positions(i.e <msg type>_error)
--> FIDCC1_ERROR for FI
--> WMMBXY_ERROR for GR
--> couldn't find PO tasks PORDCR_ERROR, PORDCH_ERROR
Can I assign a task group for the admnistrator?
Can someone lead me in right direction to fill gaps?
Thanks

Hi,
If each partner profile (or each message level within one partner profile) is to be assigned to a separate group of users, you can assign the respective positions (with the group of users included in the position) in the partner profile itself. (Instead of 'user' choose 'position' and specify the position you have created, in the partner profile settings where you are specifying users now). You can do it at the partner profile level, or at the individual inbound message level in the partner profile (Post processing agents in the detail settings screen for the inbound message - specify your 'position' there).
If this is not a one to one (by one I mean a position and not a single user) assignment, you will need to assign agents at the task level.
You can see all the standard tasks in SWE2 for example. Choose your business object (eg BUS2032 for purchase order) and corresponding task there. You can assign agents to these standard task in PFTC. For example, if a PO failed, task TS00008097 (in PFTC) which is based on errors encountered when creating a PO, will be triggered and the corresponding IDOCs can go to the assigned agents.
You have to note that the agents who receive the workitem is a intersection of these two assignments. So, let us say if you have assigned EDI_PO_SUPPORT at the task level, and CCD_PO_SUPPORT at the partner profile level, then the users common in these two positions will only get the workitem.
I have not looked into 'assign tasks to positions' as I have no experience in that. However, using the above, you can just create positions with users (do not bother about assigning these positions to any task), and assign that directly either at partner profile level or at task level, nothing else is required.
Hope this helps,
cheers,
Ajay

How to block the status mail for an inbound Idoc to a specific user

Hi,
I have to stop sending the error status mail to a specific user depenidng on Partner Type. This will trigger when an inbound Idoc contains status error(message type INVOIC &ORDRSP).This user needs other mails which are getting triggered with the same Idoc for the same partner. Basically, the requirement is to block only the status mail for that user. The statndard task for this is TS70008125 and it uses the agent determination rule 30000001 (Idoc Administrator).in WE46, this task is assigned to process code EDIR. I have copied the task to a custom task and changed the agent determination rule. I would like to know how will I configure this task so that this custom task will trigger for the status error, without altering other workflows for the same message type & the partner type. Or is there any other way to block the mail?
Thanks,
Santosh

Hi,
I have done the required coding to exclude the specific agent from the rule,copied the task and its ready. My question is how do I map this custom task to a particular partner type, for the message type INVOIC in WE20? (The message type used for the inbound Idoc is INVOIC). I checked the Partner profile in WE20. Most of the process code is using function module as the processing type.
Thanks,
Santosh

Using Inbound IDOC from Java system creation of Outbound delivery

Dear Experts,
The scenario we are having is really very interesting. Hopefully its a good learning for me and also for others also.
The scenario is,
After sales order creation the details will be sent to one Non SAP system (Java) for performing some tasks related to forwarding agent decision, shipping date and etc. Once the details are finalized in that Java system then, the details needs to be transferred to SAP as "Inbound IDOC" process. For this proposed to use the SAP Jco middle ware.
Once the details transfered from Java system to SAP then, the outbound IDOC needs to get generated automatically. Assuming the stock for that sales order line item is available. Also one more complexity is, our client is using custom transaction (ZVl10C) for delivery creation.
Now Query is,
1. Which IDOC, message type and Functional module needs to be used for creating the delivery automatically..??
2. As per assumption, stock of that sales order line item should be available. Due to some business reason the stock was removed during inbound IDOC transfer then, what will happen to the IDOC..?. How to avoid this situation..??
3. As we told we are re going to use SAP Jco b/w SAP & Java system. In this case, how the data will get transfered from Java system to SAP..?
Thanks in advance for the replies I am going to get
Regards,
VEL

Thanks for the feedback. This question is resolved

Outbound delivery creation with inbound IDOC transfer from Java system

Dear Experts,
       The scenario we are having is really very interesting. Hopefully its a good learning for me and also for others also.
The scenario is,
               After sales order creation the details will be sent to one Non SAP system (Java) for performing some tasks related to forwarding agent decision, shipping date and etc. Once the details are finalized in that Java system then, the details needs to be transferred to SAP as "Inbound IDOC" process. For this proposed to use the SAP Jco middle ware.
             Once the details transfered from Java system to SAP then, the outbound IDOC needs to get generated automatically. Assuming the stock for that sales order line item is available. Also one more complexity is, our client is using custom transaction (ZVl10C) for delivery creation.
Now Query is,
               1. Which IDOC, message type and Functional module needs to be used for creating the delivery automatically..??
               2. As per assumption, stock of that sales order line item should be available. Due to some business reason the stock was removed during inbound IDOC transfer then, what will happen to the IDOC..?. How to avoid this situation..??
               3. As we told we are re going to use SAP Jco b/w SAP & Java system. In this case, how the data will get transfered from Java system to SAP..?
Thanks in advance for the replies I am going to get
Regards,
VEL

Didn't get any feedback from experts for long time. So we are closing the question

Inbound IDoc w/message ORDERS - issues with error processing

We are using inbound IDoc ORDERS05 with message type ORDERS to create the sales orders in SAP. In WE20 we have the following settings:
- partner type LS (= Sales Org VKORG)
- process code ORDE
- trigger by background program
- post-processing agent of type US (user) with a user ID.
We create IDocs through an ABAP program and use RBDAPP01 to post the IDocs. When there is an application error in the IDoc posting we expect the designated user to receive a workflow item in the SAP Inbox, but for some reason this is not happening.
I did some research and went through all the possible settings for workflow, task, etc. and everything seems to be set up correctly. When debugging RBDAPP01 I have noticed that it calls FM APPLICATION_IDOC_POST_IMMEDIAT, which, in turn, calls IDOC_START_INBOUND. If IDOC_START_INBOUND returns SY-SUBRC = 1 then the workflow item is sent correctly to the designated user, exactly as we want. But for some reason it returns 0 (I changed it to 1 in the debugger).
It seems that IDOC_START_INBOUND reads TEDE2 records (TEVE2-EVCODE = ORDE) and sy-subrc = 1 is only possible when EDIVR2 is 1,2,3 or 4. In our case TEDE2-EDIVR2 = 6. It seems that TEDE2 is maintained in the transaction WE42. However, I tried to change the settings there but it affects the IDoc processing in whole (IDoc gets some odd status and doesn't get processed as before). I've also tried to use process code ORDE_BY_WORKFLOW in WE20 with the same "success".
What do we need to do to get a workflow item for the errors that happen in the application layer when IDoc is posted? Is it even possible with this message type?
Any ideas would be appreciated.

Hi,
Can you please share how do you overcome the problem, so that it can be helpful for others.

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

Inbound IDOC Mass processing - No status message

Hi Friends,
I am updating a database table using inbound IDOC. But in batch job when XI passes multiple IDOCS,
for some IDOCs there is no status message even though i coded for status message.
If i rerun IDOC in BD87 then it work fine.
please help.
regards,
madan

Hi Madan,
Since you are loading multiple idoc to the system due to high load in the production system data is not commiting properly. So use external commit work statement in you code. this will reduce the performance but logic will work.
COMMIT WORK [AND WAIT].
Effect
The statement COMMIT WORK completes the current SAP LUW and opens a new one, storing all change requests for the current SAP LUW in the process. In this case, COMMIT WORK performs the following actions:
It executes all subroutines registered using PERFORM ON COMMIT.
The sequence is based on the order of registration or according to the priority specified using the LEVEL addition. Execution of the following statements is not permitted in a subroutine of this type:
PERFORM ... ON COMMIT|ROLLBACK
COMMIT WORK
ROLLBACK WORK
The statement CALL FUNCTION ... IN UPDATE TASK can be executed.
Triggering an internal event for the Persistence Service of the Object Services.
If event handlers are registered by the Persistence Service, these collect the changes to the objects managed by the Persistence Service and transfer them via CALL FUNCTION ... IN UPDATE TASK to a specific update function module that is registered as the last update module.
This executes all high-priority (VB1) update function modules in the order of their registration and in a common database LUW. If you do not specify the addition AND WAIT, the program does not wait until the update work process has executed it (asynchronous updating), but instead is resumed immediately after COMMIT WORK. However, if the addition AND WAIT is specified, program processing after COMMIT WORK will not continue until the update work process has executed the high-priority update function modules (synchronous updating).
When all high-priority update function modules are completed successfully, the statement executes the low-priority (VB2) update function modules in the order of registration together in a common database LUW.
After the execution of high-priority update function modules, the individual function modules registered using CALL FUNCTION ...IN BACKGROUND TASK|UNIT are executed in a separate database LUW for each destination.
Within an update function module started using COMMIT WORK, the execution of statements that lead to a database commit is not permitted. In particular, the following are forbidden:
Thanks,
Raghav

WE20 - post processing: permitted agent tab

Hi ,
I need to create a inbound TXTRAW message type for a comapny code which I have done. Then in the screen where you give the process code , the next tab is post processing: permitted agent tab ... here my requirement is that this mail should go to a group of people ... How do I achieve that ?
Please help.
Thank You,
SB.

Hi MxG,
I have created a Org unit "US90" ... but how do I directly assign users to that Org ? ... After creating Org ... it is only allowing to create positions .... and if I create position's (AP_US90_TXTR) and assign the users to the position ... In WE20 if I write "AP_US90_TXTR" in the agent field then it gives an error "Object type S, ID AP_US90_TXTR unknown (please observe upper/lower case)" ... So I am unable to proceed. Could you please help me?
Thank You,
SB.

Workflow - Inbound IDocs - ORDERS

Is there a way to control who will be receiving a work item based on the sales organization in IDoc type ORDERS?
We have some Customers extended to multiple sales organizations.
We would have 1 CSR per sales organization.
However, in WE20, the post processing permitted agent is Customer specific.
We are presently maintaining a position as agent type in WE20.
We assign all possible CSR's user ID to this position via PPOM.
As a result, when a work item is generated, ALL CSRs are getting a work item (evern when it does not belong to them).
How could we be more specific and, based on the sales organization inside the IDoc, only send the work item to the business workplace of the affected CSR ?
We are on ECC5
Thank you for your assistance,
Arnaud

In order to do so you have to create your own workflow and determine agent assignment based on probably Responsibility rules.
Thanks
Arghadip

Receiving error msg in user's mailbox for both Outbound and Inbound IDocs

Hi,
Whenever specific IDoc (Inbound/Outbound) gets failed then the user/org unit assigned in its partner profile should get those error messages in their inbox.
To achieve this for Inbound Idoc I have performed following set of steps:-
1. Created an object and attached it under IDOCAPPL using 'SWO1' and I have set that object type as 'To imported'.
2. I have assigned that object type to event 'ERRORINPUTOCCURRED' and standard tasks '00008068' (Inbound processing error), '00008074'
(Inbound Syntax error), '20000051' (IDoc Application Inbound error), '300000207' (Error during Inbound processing of SYSTAT01) using transaction 'SWETYPV'.
3. I have created an organisation unit with two positions and different jobs where each job has been assigned to specific tasks. User has also been assigned to specific jobs.
4. At the end of this I have assigned this org. unit to IDoc's partner profile.
But this process does not seem to be working we are not receiving any mail in agent's inbox. If someone has done similar kind of thing in past, please let me know the correct step for both Outbound and Inboud IDoc.
Thanks in advance.
Supriya

Hi,
Try this for inbound IDOC
Go to transaction WE42
Give the process code that you gave in the partner profile (WE20)
Select that row and press the details button (F2).
Next to the "Identification" field there will be push button which has the tool tip "ALE table"
Press that button
In the resulting screen..
In the IDOC section..
Give the following..
object type - "new business object that you created"
Start event - INPUTERROROCCURRED
End event - INPUTFINISHED
Hope this works..
Thanks,
Naren

Workflow for INBOUND IDOC

Hi,
I want to set you a workflow for one IBOUND idoc coming via edi partner. I want to use the organization units and then assign the user to it. what are the steps required for setting up a new workflow totally from the start for a IDOC / Message type and config.
Thanks in adv
/Manik

STEP 1.       USE   SALE -> Error Handling
STEP 2.   Go To Basic Workflow Settings.Use Auto-customise button to allow the system to configure most of the options.
STEP 3
a)Go to SAP MENU -> TOOLS-> BUSINESS WORKFLOW ->
DEVELOPMENT ->DEFINITION TOOLS->TASKS
b) Create a customised task putting IDOCCLFMAS for example   as object type and    INPUTFOREGROUND as object method.
c)Associate the triggring event InputErrorOccurred with the standard task.
d)Associate the terminating event InputFinished with the standard task
e) Assign appropiate agent to the customised task. For this GO TO
     Additional data -> Agent assignment -> Maintain
STEP 4 -- Go to transaction WE20.In the partner profile of the message type CLFMAS enter for the post processing permitted agent.Enter the agent type (Organisational unit,Workcenter,Job,Person,Position or User),agentId and the language.
STEP 5- In case of any error in processing of Idoc a workflow notification is sent to concerned agents.The message is sent to the inboxes of concerned persons which indicates which interface has erred,the associated IDOC number ,status of the IDOC and the date and time of error.
Regarding the complete set up you can check the workflow tutorial in help.sap.com.
regards
Aveek

Inbound idoc ( shipment) - Status change

Hi Experts,
I will be getting an inbound idoc containing tracking number of the shipment from an external agent.
I have to update this tracking number in the shipment and change the status of 'shipment Start' and 'Shipment End' to be completed.
1. Is this status change feasible ?
2. If so can you please guide me both to update tracking number & status .
Thanks
Seema

Hi Martin,
Thanks for the response.
Can you tell me which basic type will suit for this among SHPMNT01 to 05. I need to get the tracking number from any of the segments.
thanks
Seema

Inbound Idoc - permitted agents

Similar Messages

Maybe you are looking for