Inbound idoc testing via partner profile

i want to test inbound idoc testing via partner profile.
the problem is i its generating idoc no and giving a message like
"idoc no 12453152.. is saved but cannot or shd not be processed".
what does that mean ..
how shd i veiw properties of partner p[rofiles

i am getting thid message from we 19 ..
in that i am creating a sales order...
i am clicking on startinboung button on application tools bar.
this is an information pop up window ..
if i press f1 on that ..
help says that ...may be you cannot process the idoc immediatly...
check for partner profiles

Similar Messages

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

File to IDOC - issue with partner profile

I have done File to IDOC scenario and tested it end to end successfully. For same have done all require configuration setting in R/3 like defining logical System and partner profile. And it sends new IDOC successfully in R/3 with status code 50 (IDoc added).
But when I create new logical system and partner profile in R/3 and when I use same logical system in my above mention scenario then my new generate IDOC in R/3 return status code 56 (EDI: Partner profile inbound not available). But same scenario work fine with my earlier partner profile. Here I have done all require changes at adapter level like adapter specific identification and same new logical system I have update in SLD with my business system Logical System Name.

Hi Bhavesh,
Thanks for your reply.
In control record, I checked with sender and receiver partner. In this sender partner is new partner profile which I have created with port details. Receiver partner has logical system name which I have mentioned in my SLD for my receiver business system. But in receiver partner dont have any port details.
But still it has same problem.
-Sunil

Idoc: BS and Partner profile

Hi Experts
Does the partner profile created in R3 and the business system created in SLD needs to be the same for any idoc scenario. If yes why do we need to do so? and is it applicable for all types in partner profile?
thkx

They do not need to be the same, but it may help with a complex landscape if they are.
The systems are linked via hostname to SLD
A standard naming convention is recomended across the landscape and applied through all connections.

Inbound Idoc Testing

Hi All ,
Can anyone pls let me know how to test Inbound Idocs.
I am writing a ZFM to process orders01 idocs coming from the external system. After writing the code, how can i test the same for the IDOC that has to come . I mean to say : Idoc will not be available at the port in real time now (only once the system is up ,the Idoc really come). SO , what is the way to test the program developed for Inbound processing of Idoc of a certain type ?
Thanks,

Hello,
Use WE19, copy any existing Idoc, and then use your FM to test it.
If there isn't any then make an file on the server, which actually will be generated by Outbound processing.
Regards,
Naimesh

Settings for IDoc Processing Maintain Partner Profile Manually

Hi Everybody,
I just wanted to maintain a partner profile for IDoc Outbound Processing in CRM7.0. The Partner Type is LS (Logical System).
Now, when I'm creating an Outbound Parameter and want to save, I get an Error Message that the field package size must be > 0.
The problem is, that there is no field Package Size. In older systems there is such a field under the field receiver port.
Anyone any idea where is the missing field or another solution.
Thanks and regards,
Sebastian
PROBLEM SOLVED !!
When you get the error message, press enter several times and the field appears. Incredible.... but true.
Edited by: Sebastian Wilhelm on Sep 3, 2009 4:06 PM

Hi,
Steps to do ALE Configuration with respect to IDOC:
Configuration in R/3:
1. Create a RFC destination using Transaction = SM59
2. Create the ports using we21 and refer the port to the created RFC dest in above Step.
3. Create a Logical System using Transaction BD54.
4. Create a partner profile using transaction WE20.
Also need to configure in XI:
1. Create a RFC destination using Transaction = SM59
2. Create the ports using Transaction IDX1 and refer the port to the created RFC dest in above Step.
3. The port has to be displayed in the IDX2 transaction and we should be able to view the idocs which we imported through integration repository otherwise we have to manually import the idocs from IDX2 using the port created above
Also refer to the link below for further details:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Regards,
Nithiyanandam

Inbound Idoc Testing File Template

Hello friends,
Could any one guide me in preparing the Test file for testing Inbound IDOC (message type: ACC_DOCUMENT) and (basic type: Acc_Document01).
Only these are the 4 segments I am going to use.
E1BPACHE09
E1BPACGL09
E1BPACAR09
E1BPACCR09
Basically I would like to know how to create a template to upload multiple documents during testing and the procedure to upload.
I am able to test post one document at a time thru WE19.
Thanks for ur help.
Sam.

Hi Sam,
Try this, to my knowledge this is only to test if idoc is posted properly or not (to check the configuration), we can only post one Idoc at a time i think...but try this...
am not sure but try this...
Go to WE19-> acc_docume*>control on the data segment and copy it->insert(next to copy in menu bar) the segment at the same level> fill the data and post it ...to see..just try this...
Thanks
Ajay

Using SYPART01 IDOC for setting partner profiles from external system

We wish to maintain our partner profiles from an external system.
Is there any existing interface for doing this.
It seems that the sypart message is only for output, not input.
Any ideas or suggestions?
Thanks!
Dan

Hello Dan,
Thanks for your post.
I hope the following code helps in future.
http://wiki.sdn.sap.com/wiki/display/Snippets/Copy+partner+profiles+with+SYPART+message+quickly.

Duplicate message checking for inbound idocs sent via http protocol

When our warehouse system sends inbound WMMBXY idocs to us it appears to be checking an internal table in SAP to make sure that the message has not already been processed. This check appears to be related to a unique message ID that is originated by the DC system. This message ID does not appear in the actual idoc it appears to have been removed prior to the idoc being created.
When we restore production data into a test environment we occasionally have problems where the warehouse system fails to post WMMBXY messages with a "Idoc already posted" type message. Can someone tell me where the file is on SAP that holds a log of already processed messages - so that in such cases I can make sure that the warehouse do not send duplicate messages.
Many thanks, John.

hey
if you wanna see your messages you may look in table SXMSPMAST
also have a look at the following thread
In Which Database Table the Messages are Stored in XI
Thanx
Ahmad

"error no:58" partner profile not maintained in idoc.

Hi to all,
i am new member to this site already searched forums for solution.
can anyone help us out to solve the following error while simulating inbound idoc.Error:58 " partner profile not maintained"
we tried with msg type CREMAS and DEBMAS.created partner profiles,rfc connection as procedural but same error results.
also give some useful links to process idocs.
we want ur valuable suggestions,thanks in advance.
regards
vinoth

Hi,
link for inbound idocs is given below
[http://help.sap.com/saphelp_46c/helpdata/en/78/2174b051ce11d189570000e829fbbd/content.htm|http://help.sap.com/saphelp_46c/helpdata/en/78/2174b051ce11d189570000e829fbbd/content.htm]
[http://sapdocs.info/sap/abap/idoc-useful-notes/http://www.scribd.com/doc/24447/SAP-R3-IDoc-Cookbook-for-EDI-and-Interfaces-by-Axel-Angeli|http://sapdocs.info/sap/abap/idoc-useful-notes/http://www.scribd.com/doc/24447/SAP-R3-IDoc-Cookbook-for-EDI-and-Interfaces-by-Axel-Angeli]
[http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-part-ii/|http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-part-ii/]
[http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-part-iii/|http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-part-iii/]
Please check in the receiver side if the partner profile is configured correctly.
Go through the link below in order to maintain partner profile.
[http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/content.htm|http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/content.htm]

Partner Profile in Idoc

Hi ,
I have created a partner profile of type logical system. If i dont specify anything in the inbound parameters and send an idoc to this partner profile then how would the system respond.
Regards
Arun

INBOUND processing the IDOCs are transferred to the interface and stored in te SAP system. The document data is generated in the course of workflow.
In this section the SAP system is made known to the upstream system (startrfc program parameters). Conversele, the upstream system is made known to the SAP System via the port definition.
INBOUND Processing - Create Function Module.
This function module is called when a message type, of the ZINVRV, comes into the receiving system. This needs to be configured. The function module is passed the IDOC as a parameter.
Use the T.code WE19 to test inbound function module in debugging mode.
Use the T.code EW05 to view the IDOCs and their statuses.
Rewards if useful.

EDI: Partner profile inbound not available Message no. E0337

Hi Friends,
I am facing very wiered issue for incoming vendor frieght invoice. When the IDOC is sent to SAP from the edi subsystem, it gets posted with status 56 and error message
EDI: Partner profile inbound not available
Message no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/0040000010/LI/VN/INVOIC/MM///
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST test flag
I have created the partner profile in WE20 for Partner type LI, partner role VN and process code INVL, message type INVOIC, message code MM. I have also checked the entry in TABLE EDP21 and the entry exists.
When I open the IDOC in WE19, and click on standard inbound TAB it says partner profile not maintianed, however when i click on the control record it opens a dialog box, where we have all the entries for partner profile and when I just click on any field in the dialog box and click continue and when again click on standard inbound it say partner profile maintained.
None of the data is changed in the IDOC control record, I just click on any field and it finds the partner profile.
Please let me know your thoughts, what could be possible reason and a solution.
Thanks
Deepak

Hi Deepak,
I am facing the same problem with a different message type.
But same effect. I can copy the IDoc with WE19 and it will process nicely, completely unchanged.
Have you found the reason for this?
Thanks,
Florian

Trying to change Inbound IDOC to Outbound IDOC for testing....

Hi Friends,
I am trying to do the following
1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
HELP!! Rewards

Hi Friend,
        The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
Use
You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an empty IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
Activities
·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the file type. The default file is the inbound file entered there.
·        You generate the IDoc using .
The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
·        Click on the white fields to change data in the segments.
In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
·        The additional procedure depends on whether you want to test inbound or outbound processing.
Test: Outbound Processing from MC
Use
Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
Prerequisites
You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
·        Customer or vendor records
·        Material records
·        Info records
·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as messages from the respective application.
The appropriate file ports and partner profiles must exist in the IDoc Interface.
Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to 1 (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
Activities
Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
Use
This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
Prerequisites
You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to Collect IDocs in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode Collect IDocs in live operation.
Activities
You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
You can decide whether the output mode is set to Start subsystem or Do not start subsystem in the partner profile. This defines whether the external (sub) system processes the IDocs further.
Use
This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to File.
Prerequisites
A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are credited to the relevant IDoc in the form of status records in the SAP System.
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
Test: Inbound Processing: Modified Outbound File
Use
This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to File.
Prerequisites
You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type File must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
Standard inbound processing is then triggered;
·        Reading the modified file
·        Generating the IDoc(s) in the SAP System
·        Processing in the application
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
The recipient in this case is the SAP System. The port is used for identification purposes:
·        SAP (for example RSMITH
Test: Inbound Processing: Original Inbound File
Use
This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
Prerequisites
You require a correct inbound file. In this case, correct means that the:
·        Sender and recipient in the control record are correct
·        Direction in the control record is set to 2 (inbound)
·        Client in the control record and data records are correct or empty
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
The file is deleted after being read successfully!
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
·        Inbound port
·        Name and directory of the file
These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
Thanks

Idoc setup::Partner profile for Logical system

HI All,
I am using Idocs to transmit my invoice details from ECC to PI, but every time I do this for a new customer I have to setup a partner profile for the customer whose invoice is to be sent. I setup the partner profile using WE20, I setup the partner profile for partner type KU(Customer) in the we20,
Is there any way we can setup partner profile for LS(Logical system) in we20 & I don't have to setup partner profile for each & every customer for which Idoc is to be generated.
Please provide some useful information/help to handle this business scenario.
Regards,
Saurav Singh

Hi Saurabh,
Please refer SAP Note 1103146 and check.
Please also refer the below link:-
http://www.sapgeek.net/2011/07/sap-idoc-tutorial-maintain-partner-profile/
Thanks & regards,
Rahul Verulkar

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

Inbound idoc testing via partner profile

Similar Messages

Maybe you are looking for