Authorization problem for idoc scenario

HI,
Can some one tell me what are the authorizations required to post a custom idoc to R/3 from XI ? I have done a scenario like file->IDOC(custom).When i execute the scenario it is successful in MONI. When i execute the transaction IDX5 in XI, i am seeing the status as No authorization to send IDocs with message type ZMASEMPDETAILSMT....Any help on this will be appreciated.
Regards,
Sudheer.

Hi,
Please check SAP/ERP
WE20 navigate to logical system and check the INPUTPARAMETER (ZMASEMPDETAILSMT must be a value there)
ON XI check WE21 (define a port to your ERP)
On XI create CC IDOC receiver and point to this port
Helpful Link:
https://websmp202.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700003604082004E
Daniel

Similar Messages

Problem with IDoc scenario - IDocs do not aarive to XI

Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.

Hi Olian ,
just check if u have followed all the following steps
SAP XI
1) RFC Destination (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.
2) Create Port (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 SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name
Regards,
AshwinM

Business system name important for IDoc scenario message routing?

Hello all,
I have following problem.
I have to setup with our client an IDoc scenario which is a little difficult.
The client sends project IDocs from Client ERP system to his own XI system next to our XI sytem and at last Internal Order IDocs to our ERP system. We use for each environments (DEV, TEST, PROD) a separately SLD, the client a central SLD. In each environments we use the same business name for our XI system "BS_XI". Now the problem. The client aren't able to configure two times the same business name "BS_XI" for routing to our TEST respective Production environment. DEV will not used. I know the B2B scenario should be used in this case but i have no chance to think about this. Manager decision!
So what can be the workaround.
I think about to provide our client a different Business system name "BS_XI_PROD" with different technical system informations for our PROD environment. So for my understanding, the business system name is unimportant in this case, important here the technical informations which you are able to see in "Display Adapter-Specific Identifiers". Technical system, Port and RFC configuration.
The namings convention for Business system is unimportant in this case, yes?
Many thanks in advance!
Regards,
Jochen

Dear Jochen,
Can you please clarify a bit? Is it a problem between customer's XI system and your XI system?
I think you can use Parties here. In the Party you can define some additional identifiers, with which you can differentiate the incoming IDocs.
(e.g.: in the identifiers tab, Agency=BS_XI, Scheme=ALE#KU (defined in the customer's partner profile), Name=a defined name in the IDoc control record)
So with this you will have a "Business System+Party" as an identifier, where you can use several parties with the same business system.
I hope it helps!
Regards,
Andras

Archive Link Authorization problem for Business Partner.

Hi Experts,
Currently we are attaching documents to respective objects through Tr. OAWD & these documents are available in service for object as attachment, until this it is working fine.
But we are facing problem of authorization for archive link of ISU- Business Partner. Letu2019s say we had two users USER-A & USER-B responsible to upload documents of Business partners started with 1 & 2 respectively.
We needed authorization control for USER A&B so that,
USER-A should upload documents for Business Partner 1001 to 1999
& USER-B should upload documents for Business Partner 2001 to 2999
we need to know can we restrict USER A&B so that they can not upload documents for Business Partner for which they are not responsible. we allready checked the roles "SAP_BC_SRV_ARL_* " but not found useful to restrict USER A&B.
Thanks in advance....

Hi Sam,
as this sounds like you search for suitable authorization objects I think that the authorization trace in transaction ST01 could be useful for you. For further information please see the following link: http://wiki.sdn.sap.com/wiki/display/PLM/AuthorizationTraceintransactionST01
Best regards,
Christoph

Communication Channels for IDOC scenario

Hi!
I have a conceptual question regarding the communication channels within IDoc scenario.
Case 1:
- File_to_RFC scenario
Here I defined a File communication channel from business system A.
1a) For which system (business system A or B) do I need to define a IDoc communication channel?
1b) What is the RFC destination and Port I need here?
Case 2:
- IDOC_to_IDOC scenario
2a) Do I need in this scenario only one communication channel for business system A?
2b) What is the RFC destination and Port I need here?
Thank you very much!
Thom

>
Thom Heinemann wrote:
> Hi!
>
> I have a conceptual question regarding the communication channels within IDoc scenario.
>
> Case 1:
> - File_to_RFC scenario
> Here I defined a File communication channel from business system A.
> 1a) For which system (business system A or B) do I need to define a IDoc communication channel?
> 1b) What is the RFC destination and Port I need here?
>
in this case no IDoc CC is involved. All you need is a File sender adapter and RFC receiver adapter
> Case 2:
> - IDOC_to_IDOC scenario
> 2a) Do I need in this scenario only one communication channel for business system A?
> 2b) What is the RFC destination and Port I need here?
>
>
> Thank you very much!
>
> Thom
in this case you will need a IDoc receiver adapter only.
The basic settings:
In XI
SM59 - R3 connection pointing to R3
IDX1 - define the port with the above dest.
In R3
SM59 - R3 connection pointing to XI
WE21 - define the port with the above dest.
WE20 - Partner profile type outbound/Inbound
Further ref:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&

Steps for IDOC scenario

Hi all,
I am doing an File to IDOC scenario.I have done with all the mappings and configurations in IR and ID.Please can anyone let me know the configurations that are to be done in R/3 and SLD for the posting of IDOC.
Please can anyone explain this to me.
Awaiting for ur reply
Amit

Hi Amit,
the following is from a thread/blog I cant find anymore. So I copy and pasted it!
SAP XI
1) RFC Destination (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.
2) Create Port (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 SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Regards Mario

Problem in Idoc scenario

Hi
Can anyone tell me how to determine the status of an iDoc in recieving system.
Please be specific

Hi,
enter WE05 transaction code in R/3 and hear u will c the status of IDOC wether it is posted succesfully.
1. Start with checking the status in sm58 of sender R/3
Follow the steps
No message in found in XI in IDOC to FILE scenario
2. Try deleating the IDoc from IDX2 and refiring the same.
3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
4. Monitor the SM58 in R/3 for IDOC status.
5. Trouble shooting file to IDOC and IDOC to file
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
Refer below links for indepth troubleshooting
File to IDOC, trouble shooting
Refer below steps
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOC to File steps to be followed please verify your scenario with it
R3 system.
1. Create SM 59 RFC destination to XI,.
2. We21 - Create port to XI.
3. We 20 -- Maintain Partner Profile for the outbound Idoc.
XI SLD
1. Create technical system for R3 system
2. Create Business System for the Client of the R3 system.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
These are the required steps for IDoc to File scenario...
In R3 (i.e., your IDES system)...
RFC dest to XI (sm59) - any name
Logical system (bd54) - any name
Port to XI (we21) - any name
Partner profile for the logical system (we20) - use Logical system name created in bd54
In XI...
RFC dest to R3 (sm59) -
Port to R3 (idx1) -
create metadata for the idoc (idx2)
In sld...
create business system for R3 with Logical system name as r3 sys.
In we19
and give in control record as
Sender : Port ; Partner
Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
see the below links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario

Authorization-problem for standard users when running WDR_TEST_ZCI

hi
we've developed a WDA application incorporating several interactive forms. it all runs fine in QA--environment when a user with developer-role are running the application, but when standard users are running it, it fails.
the same happens with the demo-app WDR_TEST_ZCI.
i so belive this to be caused by missing authorizations for the users. can anyone shed any light on which these might be?
the error as reported in the browser:
The following error text was processed in the system Q97 : Access via 'NULL' object reference not possible.
The error occurred on the application server xx-x168_Q97_05 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: PARSE_XML_SCHEMA of program CL_WD_ADOBE_SERVICES==========CP
Method: GET_SCHEMA_VERSION of program CL_WD_ADOBE_SERVICES==========CP
Method: CONSTRUCTOR of program CL_WD_ADOBE_SERVICES==========CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/LADOBE==================CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/LADOBE==================CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L7STANDARD==============CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
any input appreciated.
cheers
tom

Hi Tom,
When you are familiar with authorizations in PFCG trabsaction you are finaliar with S_DEVELOP if not ask the authorization team on your project.
Basically this authorization object handles the read/write etc authorization related to devlopment objects. If you implement Adobe forms you will probably develop your own forms or at least copy the SAP forms to customer namespace.
For Adobe you will therefore have 2 custom development objects (1 for the form and 1 for the interface that is automatically generated). The end-user shoulf have at least READ access to these objects. If not the portal will trow an error on this.
To determine the tech names of the objects find the form and related interface in transaction SFP. These should be inserted in the object S_DEVELOP in the role for the end users.
You may want to consider to put the value Z* in the object which will give authorization for all the custom developed objects.
If you can't find the object reply again and i will send a screenshot.
Finally, make use of the splended transaction ST01!! It will make your life a lot more easy in portal! It traces all the authorizations needed and missing for any user you specify. After activating the trace and running a portal scenario the log will tell you want went OK and what not on an authorization object level.
Good luck,
Thomas
ps. Thanks for the appreciation you gave in my other thread. Now we have the answers in both threads as well. Take Care.

Mapping problem for IDOC Type DESADV

Dear all
I need to change Segment E1EDP07 in the message type DESADV.
I should concatenate VBELN and VGPOS into BSTNK.
I tried to do this with BD79 (Rules for Data Converting). This seems not to work as I can get only 1 sender Field.
So I tried to use the userexit EXIT_SAPLBD11_001, but it seems that this is not used. I have set a break-point for debugging and treated the IDOC with RSNAT00 without any stop.
Do you have any ideas how I can do this?
Herbert

>
Herbert Schlup wrote:
> I have 2 entries for my DWSADV01
>
> 1 with FM IDOC_INPUT_DESADV and the other with IDOC_INPUT_DESADV1
With the first one, you cannot do much, as there is no user exit in it. But in the second one, there is a user exit when the idoc data is parsed the exit name is EXIT_SAPLV55K_004 and is called in the subroutine DESADV_IDOC_PARSE in the function.
But please note that the function IDOC_INPUT_DESADV1 is used with process code DELS for message type DESADV and Idoc type DELVRY01 and IDOC_INPUT_DESADV is used with process code DESA and message type DESADV with IDoc type DESADV01. So you might be using IDOC_INPUT_DESADV function and unfortunately there are no user exits to handle your requirement.
My advice would be to check with the source system or the middleware to define the mapping of these fields according to your requirement. But if that is not possible, then you need to first check which message type and IDoc type you are receiving and proceed accordingly
KR,
Advait

Inbound Queues getting stuck up in PI7.1 for Idoc scenario Mpackg. enabled

Hi Experts,
We have an issue while processing Single Idocs in PI 7.1.
we have extended MATMAS05 and we are processing these via PI to FTP folder.
The inbound queues are frequently getting stuck.we will be sending atleast 1000 idocs every hour from R3.The processing time is very slow for this interface and its impacting other interfaces which we are currenlty having.
We have followed the webblog by William Li "Step-by-Step Guide in Processing High-Volume Messages Using PI 7.1's Message Packaging" but still the processing time for Single Idocs is very slow.
We have to use single idocs as we will send only the changed materials from R3.
Could you please assist us in overcoming this issue.
Many thanks in advance.
Points will be awarded for valuable feedback.
Cheers
Jyoti

Hi Jyoti,
Message Packaging works PI7.0 SP 13 and PI7.1 .
we have to configure Message Packaging manually ,
Step 1) 1. Enable packaging for the integration server
SXMB_ADM -> Change Configuration (F9), create a new entry:
Category: RUNTIME (PI7.1)
Parameters: PACKAGING Current Value: 1 (for active) .
Default Value in PI7.0
Current Value: 0 (for inactive)
Step 2) Create "Package Configuration Type u201C
Use Transaction SXMS_BCM .
Configuration Type : Any name.
Description: any text to describe the configuration type .
Wait Time : 60 seconds
Number: 100
Maximum Package Size. 2 MB
Step 3) Create "Sender/Receiver Definition
Transaction :   SXMSIF (Create New Entry).
Sender/Receiver ID:PACKAGE_DEMO .
Description :
Interface Name: Interface Name used in Receiver Determination.
Interface Namespace:   Interface Namespace used in the Receiver Determination .
Step 4: Create "Specific Package Configuration"
Transaction :    SXMS_BCONF .
Step 5: Package Monitoring
TX: XMSPKSTATCNF
Follow above steps and configire message packaging , then you feel diference,
actuualy i configured message mackaging,i am feeling the difference.
if any issues let me know.
Cheers,
Raj

Authorization Problem for Ztcodes

Hi All,
I m having a problem in zdevelopments that every user can access these
T-code without any authorization. I want that there should be proper autorization to access these tcodes like standard tcodes. when i told to basis guy to restrict these tcodes , he is not getting these tcodes in his roles & authorization group. How can i do that. Plz help me .
Thanks in Advance
Jitendra Singh
9999966736

aa

Authorizations problem for Product Hierarchy

Hi,
We have a requirement in which we need to restrict authorization for the product hierarchy based on secret products. The material object has an attribute called secret indicator which has Y/N values. We need to restrict the users based on this attribute. The restriction should be such that the users should not even be able to see the nodes for secret materials in the product hierarchy if they are not entitled to it.
Any pointers ?
Thanks
Shailesh

Can you create two different hierarchies, one with secret nodes and one without? Then you could create an authorization object on the Secret attribute and check the authorization in a user exit.
You would then use a user-exit variable that is filled automatically (no user input) and fill it depending on the authority check with hierarchy 1 or 2.
You could also write an ABAP that filters the secret products out of the first query. It is a bit complicated.
Best regards
Dirk

Doubt regarding ALE SETTINGS in IDOC scenario.

Hi Friends,
        I have some doubts regarding ALE settings for IDOC scenarios, can anyone please clarify my doubts.
For exmaple take IDOC to FILE scenario
The knowledge i got from SDN is --
One need to do at the R3 side is --- RFC DESTINATION (SM59) for the XI system.
                                                   --- TRFC PORT for sending IDOC to the XI system
                                                   --- CREATING LOGICAL SYSTEM
                                                   --- CREATING PARTNER PROFILE
               at the XI side is --- RFC Destination ( For SAP sender system)
                                       --- CREATING PORT for receiving IDOC from the SAP sending system(IDX1).
1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
In IDOC to IDOC scenario-------
2. Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
3. If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
y we r creating receiver communication channel in the case of FILE to IDOC scenario?
4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                FILE to IDOC scenario,
IDOC to IDOC scenario individually.
Thanks in advance.
Regards,
Ramana.

hi,
1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
it is a mandatory step in doing ALE configurations
2. We create 1 RFC destination each in R3 and XI.
    R3 RFC destination points to Xi and
    XI RFC destination points to R3
3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
4. ALE settings for all IDOC scenarios are same as follows....
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful
Prashant

Separation of business processes in IDoc scenarios

Hello!
We have implemented an IDoc -> XI -> IDoc scenario with complex mappings and enhanced receiver determination using the value mapping API in which about 15 different R/3 platforms send IDocs to XI for internal ordering.
All R/3s are using standard IDoc types like DELFOR.DELFOR02, DESADV.DELVRY03, ORDCHG.ORDERS05, ORDERS.ORDERS05 and ORDRSP.ORDERS05. As XI gets more and more used additional projects are coming up in which we will also use exactly the same IDoc types.
Especially when using enhanced receiver determination it now gets extremely difficult to separate the different business processes once they use the same IDoc types. The projects do not only share the same receiver determination object but what is even worse they also share the same message mapping object to determine the receiver. This makes development, testing and MTP extremely difficult and requires coordination over several project teams.
Within R/3 business scenarios can easily be separated using different message codes and message functions. However, once the R/3 post IDocs to XI there is no clear separation possible any more.
Of course, every project can implement own Java classes for enhanced receiver determination and transport the archives separately but still the problem is that all the projects using the same IDoc message type share the same message mapping object to the determine the receiver. This means that it would be necessary to fill the input parameters for the enhanced receiver determination classes of ALL projects within the same object. Either by putting logic in the graphical mapping or writing another Java function to call the different Java classes for enhanced receiver determination based on the message code and message function.
From a design perspective it is no good approach to mingle logic for different projects and business scenarios in the same development objects. What alternatives do we have? Does SAP plan to support a separation using message code and message function for IDoc scenarios in the Integration Repository?
Regards, Tanja

Hello!
Does nobody have any comments on this?
Regards, Tanja

Idoc Scenario Partner type not LS

Hi experts ,
we have gone through https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a&overridelayout=true for idoc scenario where idoc partner type is not a logical system .Now we are working on case2 scenario in above document.we have some confusion in the configurations at R/3 side.Can somebody explain the step by step configuration at R/3 side.
Thanks.

Hi Mark,
For your requirement you, create partner profile for LS with following steps :
Create New Partner profile and give your respective TY (User Type), Agent & Language and then follow maintain following parameters under Outbound Parameters :
Message Type      : INVOIC
Under Outbound Option u2013 Tab
Receiver Port      : <Mention your receiving port here, to create Receiver port you have to go to WE21 transaction>
Pack Size           : 1
Transfer IDoc Immediately (Select)
Basic Type           : INVOIC02
Cancel Processing After Syntax Error (Select)
Under Message Control - Tab
Application           : V3
Message Type      : RD00
Process Code           : SD09
Hope, your problem will get resolve.
Regards..
Imran

Authorization problem for idoc scenario

Similar Messages

Maybe you are looking for