Transaction SALE - Inbound SOAP for IDOC: Register Service

Hi,
Does anyone have some information on this feature in ECC 6.0?
Ron

Hi Advait,
Did you get any further with this problem. I have the same issue and I don't know how to go further on this
Ron

Similar Messages

Inbound SOAP for IDoc : Register Service

Hi ,
We have a requirement where we need to post an Inbound IDoc in the R3 from a Web Service that is called from a 3rd party application, I found something in the Transaction
SALE->Basic Settings-> Inbound SOAP for IDoc : Register Service in R3 , the documentation says "You execute the report SRT_REGISTER_SERVICE to activate Inbound SOAP for IDocs." But I'm confused what needs to be done after that.
Can anyone throw some more light on the following issues :
a) where does the WSDL get stored for the IDoc,
b) how to register a particular IDoc as a web service such that it can be called from third party system.
Thanking all the experts in advance for their valuable time and help.
Regards,
Advait.

Hi Advait,
Did you get any further with this problem. I have the same issue and I don't know how to go further on this
Ron

Inbound logic for idoc

hello experts,
I have a query regarding inbound idoc.The input file is placed at application server and i need to read it and post it in SAP.My queries are:
1. In order to create an idoc using the file, we will use program RSEINB00 which will create idoc's with status 50 and then i need to link the correspiodning Function module in partner profile's inbound type and set it to automatic so that it gets posted into SAP? Is this correct? If yes, does it mean that there is no custom code needed for this case(Assuming that the FM linked in WE20 is standard)?
2. Can we dynamically process the file?Meaning, as soon as the file is placed at application server is there a way to invode the program RSEINB00 automatically
or should we run it manually ?
Please help with the process pls as it is slightly confusing.
Thanks,
Prem

yes your understanding is right and if you want the files are pulled from the server automatically then you run the report RSEINB00 in a job or you can create workflows for this.

Inbound file for IDOC processing

Hi SAP Gurus,
I want to create an IDOC by using INBOUND FILE option in WE19. Can anybody suggest, how the flat file will look like ?
FYI, my Idoc type is BBP_PCSTAT01 ( Procurement Card Statement).
Any idea ?
Thanks and Warm Regards.
Pras Durafe

This is an example of idoc with flat-file:
EDI_DC40 100000000000413988546B 2 INVOIC01 INVOIC MM E97A INVOICSNDPRN LIRS86092747 SAPITZ LS CLNTITZ100 20040210105203
E2EDK01005 100000000000413988500000000000001 USD INVO4139885
The first record indicate the header data; after this, for each segment type, the information about the segment.
If you send me your email address, I can send you a complete example file.
Gianluca

Inbound FM for IDOC OILBL_RECEIVEDETAIL01

Hi Gurus,
We are going to create the locations(O401), using IDOC OILBL_RECEIVEDETAIL01.
but I did not find any inbound FM and process code for the same.
Please help .
Thanks & Regards,
jitu188

Hi Sunil,
Looks like your Inbound side COnfig is still Incomplete as you are still tryint to Identify the Process Code. Pls go through below thread as it has more information regarding the enabling ALE for WorkCenter .
https://forums.sdn.sap.com/click.jspa?searchID=23909752&messageID=7198698
Pls let me know what you think.
Regards
Shital
Edited by: shital phadake on Mar 23, 2009 10:43 PM

Sales Process And EDI Idocs Integration

Hi Friends,,
Good Day To You All !!!!
Please enhance my knowledge with your valuable reply.
I am new to ABAP and would like to learn the following .
1. Sales process - Starting from the Purchase Order Till shipment is created (All TCodes and the definations of the terms used like procurement , scheduled line,handling unit and all those terms coming into picture till the Sales process comes to an end).
2 . Idocs - Transaction Codes,Definations Of Terms like message types , basic types etc, etc,
I need the above information to get a clear picture of the process taking below.
What if an interface exists between SAP and a Non-SAP system(say Siebel system ) .The customer being the Non-SAP system and the Vendor our SAP system . Then the flow of the sales process taking place , with the PO coming from the Non-SAP system through inbound idoc and immediate ATP date going from SAP through the outbound Idoc..the process continues with the creation of delivery then shipment.Each of these triggering their respective idocs .
And the idocs update the corresponding status in Siebel .
I hope you guys would have understood by now , as to why i need the information on Sales Process and Idocs.
Thanks.
With regards,
Learner .
Edited by: SAP Technical Consultant on Oct 16, 2008 9:08 AM

Hello,
         If you want to Set up an Inbound Process for Sales Order Changes, all you have to do is
1. Maintain the Partner Profiles for the Inbound Message Type & Process Code in WE20.
2. The Assignment for Function Module IDOC_INPUT_ORDCHG is already available in WE42 Transaction for the Process Code ORDC. So, you don't have to worry about setting up the Process Code.
3. Take a Sample IDoc of Type ORDCHG Message Type in WE19 and try posting it for the Given Sales Order. If you would like to know more about what it does, Post it using Debugging Mode.
            The above Process is for Sales Order Changes via Inbound IDoc. Below are the Steps for the Outbound Delivery IDoc Trigger.
1. The Process Code DELV already has the Selection Program IDOC_OUTPUT_DELVRY in Transaction WE41. So, you dont have to worry about Setting Up the Process Code.
2. Also, check your field list. Open the IDoc Type DELVRY05 in the Transaction WE60 which is for IDoc Documentation. Check if all the Fields mentioned in your the list that you want to send are available in the Standard IDoc Type. If not, create a Custom Segment in WE31 & Assign the Custom Segment at an appropriate place in the Extended IDoc Type in WE30.
     All the Standard Segments / Fields available in the DELVRY05 IDoc Type will be automatically be populated by the Standard Selection Program IDOC_OUTPUT_DELVRY. However, if you have an IDoc Extension and would like to populate the Custom Segment / Fields, then you'll have to use the Customer Exit EXIT_SAPLV56K_002 in which you can write Code for populating the Custom Segments / Fields.
3. The Most important Thing that we need to take care of is Message Control Configuration while handling the Outbound EDI Scenario.
4. You need to Set up the Output Type for the Delivery Application (V2) for which you need to maintain Condition Records so that the Output Type is proposed automatically when the Delivery is being Saved.
5. In general, the Message Control Configuration is done by the Functional Team. So, ask your Functional Consultant to set up the Message Control Configuration for the Delivery IDoc Trigger.
Hope it was clear enough.
Thanks and Regards,
Venkat Phani Prasad Konduri

Problem in SOAP to IDOC & File scenario

Hi,
My scenario is SOAP ->IDOC and FILE,when I run the scenario IDOc was processed and File was not created at the target system.I maintained LS name for sender SOAP and IDOC business service.Nothing was maintained in adapter spec identifiers for Recer business service(i.e For target File CC).This was working fine in Dev.After Importing another scenario which uses same business service,this didnt stp working?
what could be the reason?
Thanks,
RP
Edited by: RP@261 on Oct 21, 2008 10:59 PM

> my imported scenario and existing scenario in QA using same sender business service.After importing the other scenario,existing scenario is failed to create files at target system even though it shows successful in MONI.
>
Check the target dir permission once again from your BASIS team. Reconfirm the the target dir name in receiver CC also.
> Should we maintain Logical system in adapter specific identifiers for Recr File CC also??? I create a file in BI application server from recr File CC.
>
No, for creating a file you don't require this. This is required only in case of IDOC.
> my scenario is
> (SOAP sender) --> TO IDOC & FILE ..i maintained LS name in sender BS where SOAP CC is created and also at Recr BS where IDoc CC is created. The other Recr BS for File where I didn't.IS it required ?
>
For File recever BS, No need.

Goods receipt for sales order (sample for inspection)

Hi Experts
Is it possible to enter goods receipt for a sales order?
This process is required for collecting sample from customer for carryingout testing of the sample.
Please suggest the doc types and process steps.
warm regards
ram

Hi Lakshmipathi
Thanks for your reply.
This is a sample received from a client for carrying out analysis and furnishing the laboratory test results as a Quality certificate
So, the sales order is for execution of service (Testing service).
The sample to be received in ref with the sales order and test result to be delivered to customer.
Please suggest the best possible process
warm regards
ram

Is it possible to create an inbound SOAP Adaptor for an ESB routing service

I have been given a pre-defined wsdl file that defines the inputs to an ESB service and I wa wondering whether it is possible to create an inbound SOAP adaptor or whether this is actually an outbound adaptor. I am new to SOAP adaptors so need a little bit of guidance.
Hopefully someone can help.

Hi,
In your case you need to create an Routing Service. If you create an esb project you can select Routing Service from the ESB Services entry in the Component Palette. You then get the option Select Existing WSDL. The SOAP adapter is only used for outbound SOAP messages. If you define a routing service it is available as a 'webservice' with a wsdl (in this case the one you define) from the console.
Kind Regards,
Andre Jochems

Examples needed for Idoc to file and IDOC to web services

Hi ,
Could any one of you give some examples which take me through step-by-step in building IDOC-TO-FILE and IDOC-TO-WEB SERVICES?
Regards,
XI Developer.

Hi,
For IDOC scenario you need to first do the required configuration:
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Testing purpose u can use the below method:
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters --> For Idoc sender: IDOC -file
IDOC configuration:
Please follow the below process for configuration:
Pre-requisites for Inbound IDoc to R/3 from PI:
Configuration required at Xi side:
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
Configiration required at R3 side:
Maintain Logical System for PI (SALE transaction):
Maintain Partner Profile for XI system(WE20):
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
SOAP scenario:
YOu have to first create the WSDL through ID and import that WSDL in to IR external definition.
Refer the below thread and pdf:
How to use SOAP adapter:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
SAP AII - How to consume and expose webservices ?
Thnx
Chirag
reward points if it helps.

Need all transaction codes for idocs

need all transaction codes for idocs

Hi,
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
BAPI tcode --- BAPI.
Also:
IDOC:
IDOC ADMINISTRATION
WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05 View IDocs
WE60 IDoc type documentation tool
WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing.
BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
1.4 IDOC DEVELOPMENT
BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations.
WE19 EDI test tool. Use to test inbound Function module changes.
WE31 Segment create
WE30 Create IDoc extension type
WE82 Link Release detail to Extension IDoc Type
WE57 Assign function module to logical message and IDoc type
BAPI: BAPI, SWO1.
Transaction codes Related for IDOC Configurations
WEDI: Area Menu for IDOCs
WE02: Display IDoc
WE19: ALE Test tool
WE30: Development of IDOC Type
WE31: Development of IDOC Segment
WE41: Process Codes, Outbound
WE42: Process Codes, Inbound
WE47: Status Maintenance
WE81: Logical Message Types
WE57: Assignment Messages for Appl. Objs
SM59: RFC Destinations (Display/Maintain)
SALE: Display ALE Customizing
BD54: Maintaining Logical Systems
BD67: Maintain methods (inbound)
BD64: Maintenance of Distribution Model
BD87: Status Monitor for ALE Messages
Reward points if found helpful...
Cheers,
Chandra Sekhar.

Transaction document for Idoc type

Hi Experts,
I am seeking little information about below Idoc type from POS to SAP IS Retail,
I would like to know that, what are the transaction documents generated in SAP IS Retail after executing of below inbound idoc type.
For example WPUUMS – It will create billing document for aggregate sales and material document for Goods movement.
Similarly, please help me for below Idoc type.
·         WPUBON
·         WPUTAB
·         WPUBWB
·         WPUFIB
·         WPUKSR

Hi Vanrajsinh,
I'd recommend you to go through the help.sap.com POS Inbound Interface for general information;
POS Interface - Inbound @ help.sap.com
and then crawl through related customizing in SPRO: Sales & Distribution > POS Interface > Inbound where you'll find the document types corresponding to individual IDoc types and IMG documentation per activity is also quite 'explicit'.
Not to leave you only with links, more information below but document types generated depend on the above config;
WPUBON - POS interface: Upload sales docs (receipts) non-aggregated;
Usually creates billing document and article document to post sales and goods issue per receipt, billing type and movement types can be defined in SPRO POS as above > Control Sales per receipt
WPUFIB - POS Interface: Upload Financial Accounting Interface SRS/POS
creates only FI posting (accounting documents) for pre-defined POS financial transactions; SPRO POS as above > Transaction Types for Financial Transactions and Trans.Type Cotrol of Fin.Trans.
WPUKSR - POS Upload Cashier Data
Cashier statistics, I've only used it for statistics (RIS, no transaction documents created)
WPUTAB - POS interface: Upload day-end closing POS / Payment List
Creates billing document to post payment per payment type if not already posted via receipts, SPRO POS as above > Payment List Control
WPUUMS - POS interface: Upload sales data (compressed)
as WPUBON but aggregated sales, SPRO POS as above > Aggregated Sales Control
WPUWBW - POS interface: Upload goods movements
Creates article documents to post goods movements
Note that you usually do not use all IDoc types at the same time as this would lead e.g. to posting a single receipt via multiple flows.
Hope this helps!
Regards,
Tomas

Basic transaction for IDOC

Hi all
Can any one give me the basic transaction list for IDOC??
Thanks and Regards
Arun Joseph

Hi,
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
check the following Links
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
ALE and IDOCs
iDocs
IDOCs !!!!!! need your help
idocs
ALE, EDI and IDOCS
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
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
Regards
Kiran Sure

Business service is not working in sender side but business system is working soap to idoc but why like that

i have scenario SOAP to IDOC
when i'm using business service in sender side it is getting an error as follows
sender message can not convert to ALE Logical system
in this i'm using altova spy as testing tool
my sender interface is asynchronous
but when i'm using business system everything is working fine
In sender side i'm using soap adapter,i checked the logical system everything is fine
mainly the problem is why it is working when i'm using business system rather than business service
my pi version is pi 7.0
thanks in advance
regards
satish

Hi Satish,
You are sending IDOC's to SAP system right. we should create Business system not business service.
so we should create the business system as web AS ABAP in SLD and import the same in ID.
When we create the business system in SLD the logical system name is assigned for the business system. like SAPCLNT100...It plays a key role in IDOC scenarios.
sender message can not convert to ALE Logical system
Reasons for this issue is
1) logical system name is unable to read from SLD for that corresponding business system.
Goto business system click on Adapter specific identifiers from the menu --> read from SLD.
it will automatically fetch the logical system name from the SLD.
2) Sometimes the logical system name will be deleted from the business system in SLD.
Delete the business system and re-create it, and follow the above procedure.it will resolve your issue.
Regards
Bhargava Krishna

Need information on how to create Idoc Inbound Interfaces for Business Sys

Hi,
I'm losing it.
Can anyone point me to some documentation or an example of how to create inbound interfaces for Business Systems in PI 7.1.
Here's the scenario
I'm working on a B2B integration process which sends inbound idocs to an ECC 6.0 system.
I've created the Business System communication component but under the Inbound Interfaces it is blank.
I want to have MBGMCR.MGBMCR03 as an inbound interface.
But I forget how to get it there.
For Business components you can just add the inbound interface.
I've already defined the Business System in the SLD pointed it to the correct Tech System, imported the idoc definitions in the Enterprise Service Builder and set up IDX1, IDX2 to ensure the metadata exists in PI.
But for Business systems the hep says that it's got to come from the SLD.
Outbound/Inbound Interfaces
For each business system, the interfaces that are installed on the business system are also entered in the SLD. These interfaces are displayed in this frame. You cannot add any other interfaces.
I know I've done this before, but I can't remember how.
Cheers,
John

Hi John ,
Please have a look at the following links which might be of help to you
PI 7.1 IDocs interfaces act as operations
http://www.sdn.sap.com/irj/scn/weblogs;?blog=/pub/wlg/7933
/people/peter.gutsche/blog/2008/10/27/what146s-new-in-sap-netweaver-pi-71
There is a section in the following link on IDOC , have a look at the links in that section
https://wiki.sdn.sap.com/wiki/display/XI/ImportantBlogsand+Notes
Best Regards

Transaction SALE - Inbound SOAP for IDOC: Register Service

Similar Messages

Maybe you are looking for