Details scenario navigation steps for async_sync bridge for bapi_po_create

· Integrating web application and SAP R/3 system. A third party web-based purchasing application posts XML data to the XI plain HTTP adapter for purchase order creation. The purchase order data is mapped to RFC-XML;
BAPI_PO_CREATE is then called to create the purchase order.

Hi
check this links
Demonstrating Use of Synchronous-Asynchronous Bridge to Integrate Synchronous and Asynchronous systems using ccBPM in SAP Xi - Use of Synch - Asynch bridge in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] - Use of Synch - Asynch bridge in ccBPM
Asyn - Synch BPM - Async/Sync Communication using JMS adapter without BPM (SP 19)
There is an example of the Sync/Async Bridge in th SWCV: SAP BASIS.
Namespace: http://sap.com/xi/XI/System/Patterns
Go through this link to get a good idea as to how to Define Sync/Async Communication
This blog also should give you some idea...
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
http://help.sap.com/saphelp_nw04/helpdata/en/83/d2a84028c9e469e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c4/dc06418752ef6fe10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f9/66bf40ad090366e10000000a1550b0/RN_XI_DE_neu.pdf
regards
srinivas

Similar Messages

Steps for free goods, purchase order and sales order

Hi all,
I am just starting to learn SAP and would appreciate it anyone can guide me along with navigation/steps for the below questions:
1) can we create free goods automatically when purchase order is generated?
2) Can we duplicate data from the purchase order to the inputs of sales order?
Thank you so much for your help!

Hi Experts,
I set Free Goods determination Inclusive Calculation Rule 1=Pro Rata and Cal Rule 2=Unit reference both are working fine.
When trying for cal Rule 3 it gives error message "The system determined free goods with quantity 0 for item 000010
Means for 10Ton of A product 10% means 2To are free. If I apply quantity in multiple of 10 i.e.10, 20 30 free goods are determined, delivery & billing is working well.
But if I apply 25Ton or 38ton, it is not even giving minimum discounts say for 25ton, it should give atleast 20ton equivalent fre goods. I checked in rounding rule OB90 where my company code3000 is giving 10 2 digit for USD currency. I set like this. When I checked pricing for condition type R100 it says requirement 055 not fulfilled. However I have maintained Req 055 & BaseType 28 in pricing procedure.
For cal rule 3 what else setting I should check.
Early reply with detail steps shall be highly appreciated.
Thanks

Navigation Steps

Hi all,
Could you all please give me the navigation steps for loading the data into the cube in BI 7.
I want steps after creating the cube the next procedings .
Each and every step.Please dont give me any URL's.
Thx

hi,
BW 7.0
Uploading of master data
Log on to your SAP
Transaction code RSA1u2014LEAD YOU TO MODELLING
1. Creation of Info Objects
u2022 In left panel select info object
u2022 Create info area
u2022 Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
u2022 Create new characteristics and key figures under respective catalogs according to the project requirement
u2022 Create required info objects and Activate.
2. Creation of Data Source
u2022 In the left panel select data sources
u2022 Create application component(AC)
u2022 Right click AC and create datasource
u2022 Specify data source name, source system, and data type ( master data attributes, text, hierarchies)
u2022 In general tab give short, medium, and long description.
u2022 In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
u2022 In proposal tab load example data and verify it.
u2022 In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
u2022 Activate data source and read preview data under preview tab.
u2022 Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
3. Creation of data targets
u2022 In left panel select info provider
u2022 Select created info area and right click to select Insert Characteristics as info provider
u2022 Select required info object ( Ex : Employee ID)
u2022 Under that info object select attributes
u2022 Right click on attributes and select create transformation.
u2022 In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
u2022 Activate created transformation
u2022 Create Data transfer process (DTP) by right clicking the master data attributes
u2022 In extraction tab specify extraction mode ( full)
u2022 In update tab specify error handling ( request green)
u2022 Activate DTP and in execute tab click execute button to load data in data targets.
4. Monitor
Right Click data targets and select manage and in contents tab select contents to view the loaded data. Alternatively monitor icon can be used.
BW 7.0
Uploading of Transaction data
Log on to your SAP
Transaction code RSA1u2014LEAD YOU TO MODELLING
5. Creation of Info Objects
u2022 In left panel select info object
u2022 Create info area
u2022 Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
u2022 Create new characteristics and key figures under respective catalogs according to the project requirement
u2022 Create required info objects and Activate.
6. Creation of Data Source
u2022 In the left panel select data sources
u2022 Create application component(AC)
u2022 Right click AC and create datasource
u2022 Specify data source name, source system, and data type ( Transaction data )
u2022 In general tab give short, medium, and long description.
u2022 In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
u2022 In proposal tab load example data and verify it.
u2022 In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
u2022 Activate data source and read preview data under preview tab.
u2022 Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
7. Creation of data targets
u2022 In left panel select info provider
u2022 Select created info area and right click to create ODS( Data store object ) or Cube.
u2022 Specify name fro the ODS or cube and click create
u2022 From the template window select the required characteristics and key figures and drag and drop it into the DATA FIELD and KEY FIELDS
u2022 Click Activate.
u2022 Right click on ODS or Cube and select create transformation.
u2022 In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
u2022 Activate created transformation
u2022 Create Data transfer process (DTP) by right clicking the master data attributes
u2022 In extraction tab specify extraction mode ( full)
u2022 In update tab specify error handling ( request green)
u2022 Activate DTP and in execute tab click execute button to load data in data targets.
8. Monitor
Right Click data targets and select manage and in contents tab select contents to view the loaded data. There are two tables in ODS new table and active table to load data from new table to active table you have to activate after selecting the loaded data . Alternatively monitor icon can be used
Assign points if it is helpful
cheers
SivaRaju

HELP for all 5 TYPES of STO Stock Transport Orders with detailed scenario

PLEASE help me understanding the detailed scenarios for all 5 TYPES of STO s
as in my day to day job activities , i frequently handles issues related to STO s
PLEASE HELP WITH DETAILED STEP BY STEP SCENARIOS

Hi Jagatram,
Standard SAP has the following methods For Stock transport order:
1) One Step Transfer stock without using purchasing documents; Use movement type 301.
2) Two Step Transfer stock without using purchasing documents; Use movement type 303 in Supplying plant and movement type 305 in receiving plant.
3) Using Standard Transport Order (STO) without delivery in two steps. STO created in T-Code ME27, receiving plant posts goods issue (for returns), movement type 351 and supplying plant post goods receipt from using movement type 101.
4) Using Standard Transport Order (STO) with delivery in one step. STO created in T-Code ME27, Receiving plant creates shipment and Goods issue document (for materials to be returned) with movement type 647 and goods receipt document with movement type 101 both created in one step.
5) Using Standard Transport Order (STO) with delivery in two steps. STO created in T-Code ME27, Receiving plant creates shipment and Goods issue posted (for materials to be returned) with movement type 641.Goods receipt is posted in the supplying plant, movement type 101.
6) Using Transportation scheduling agreement (TSA) with delivery in two steps. TSA created in T-Code ME37. Receiving plant creates shipment and Goods issue document (for materials to be returned) with movement type 641. Goods receipt is posted in the supplying plant, movement type 101.
To achieve it, necessary configurations has to be done in Tcode- OMGN.
SPRO>> Materials management>> Purchasing>> Purchase Order>> Set up Stock transport Order:
1. Plant: For the receiving plant, maintain customer No-Plant (If using STO with delivery), for the Sales Org, Dist channel and Division.
2. Checking Rule: Create checking rule.
3. Define checking rule : Usually no change required here.
4. Assign delivery type/checking rule: Assign the document type(UB) - Supplying plant- Delivery type(NL).
5. Purchasing document type: Maintain the supplying plant- Receiving plant relationships for the doc type-UB, either 1-step or 2-step, as per business.
Hope this helps!
Regards,
Shilpa

Please send detail steps for uploading legacy data

Hi friends,
please send detail steps for uploading legacy data
Thanking u in advance,
Diwa.

HI U CAN USE LSMW TO UPLOAD LEGACY DATA
LSMW is used for migrating data from a legacy system to SAP system, or from one SAP system to another.
Apart from standard batch/direct input and recordings, BAPI and IDocs are available as additional import methods for processing the legacy data.
The LSMW comprises the following main steps:
Read data (legacy data in spreadsheet tables and/or sequential files).
Convert data (from the source into the target format).
Import data (to the database used by the R/3 application.
But, before these steps, you need to perform following steps :
Define source structure : structure of data in the source file.
Define target structure : structure of SAP that receives data.
Field mapping: Mapping between the source and target structure with conversions, if any.
Specify file: location of the source file
Of all the methods used for data migration like BDC, LSMW , Call Transaction which one is used most of the time?
How is the decision made which method should be followed? What is the procedure followed for this analysis?
All the 3 methods are used to migrate data. Selection of these methods depends on the scenario, amount of data need to transfer. LSMW is a ready tool provided by SAP and you have to follow some 17 steps to migrate master data. While in BDCs Session method is the better choice because of some advantages over call transaction. But call transaction is also very useful to do immediate updation of small amout of data. (In call transaction developer has to handle errors).
SO Bottom line is make choice of these methods based of real time requirements.
These methods are chosen completely based on situation you are in. Direct input method is not available for all scenario, else, they are the simplest ones. In batch input method ,you need to do recording for the transaction concerned. Similarly, IDoc, and BAPI are there, and use of these need to be decided based on the requirement.
Try to go through the some material on these four methods, and implement them. You will then have a fair idea about when to use which.
LSMW Steps For Data Migration
How to develop a lsmw for data migration for va01 or xk01 transaction?
You can create lsmw for data migration as follows (using session method):
Example for xk01 (create vendor)
Initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.
1. TCode : LSMW.
2. Enter Project name, sub project name and object name.
    Execute.
3. Maintain object attributes.
    Execute
    select Batch Input recording
    goto->Recording overview
    create
    recording name.
    enter transaction code.
    start recording
    do recording as per ur choice.
    save + back.
    enter recording name in lsmw screen.
    save + back
Now there will be 14 steps.
2. MAINTAIN SOURCE STRUCTURES.
    Here you have to enter the name of internal table.
    display change
    create
    save + back
3. MAINTAIN SOURCE FIELDS.
    display change
    select structure
    source_fields->copy fields.
    a dialogue window will come .
    select -> from data file
    apply source fields
    enter No. of fields
    length of fields
    attach file
    save + back
4. MAINTAIN STRUCTURE RELATIONS
    display change
    save + back
5. MAINTAN FIELD MAPPING & CONVERSION RULE
    display change
    click on source field, select exact field from structue and enter
    repeat these steps for all fields.
    save+back
6. MAINTAIN FIXED VALUES, TRANSACTION, USER DEFINED
    execute
    save + back
7. SPECIFY FILES.
    display change
    click on legacy data
    attah flat file
    give description
    select tabulatore
    enter
    save + back
8. ASSIGN FILE
    execute
    display change
    save + back
9. IMPORT DATA.
    execute
    display change
    save + back
10. DISPLAY IMPORTED DATA
      enter ok, it willl show records only.
      back
11. CONVERT DATA
      execute
      display change
      save + back
12. DISPLAY CONVERTED DATA
      execute
      display change
      save + back
13. CREATE BATCH INPUT SESSION
      tick keep batch input folder
      F8
      back
14. RUN BATCH INPUT SESSION.
      sm35 will come
      Object name will be shown here
      select object & process

Steps for execution of valuated and unvaluated for MTO scenario

Hi,
Can any one provide the steps for execution of valuated and unvaluated for MTO scenario.
regards,
RAM

Hi,
Please find below the details about Valuated and non-valuated Sale Order scenarios:
SAP Scenario 1 - Valuated Sale Order Stock u2013 with Sale Order Controlling u2013 (MTO, ATO and ETO with VC)
1     Enquiry
2     Opportunity
3     Quotation (Creation and Approval). In case of ETO u2013 BPO is created and updated in quotation (condition type)
4     Creation of Sale Order
5     MRP Run u2013 Creation of Planned Order u2013 Creation of Production Order and Purchase Order
6     External Procurement u2013 Goods Receipt     ROH Inventory A/c Dr (BS)
     To GR/IR A/c Cr (P&L)
7     Material Consumption to Production Order     In FI:
ROH con. A/c Dr (P&L)
    To ROH Inventory A/c Cr (BS)
Same is the case with HALB
In CO:
Cost of Material is debited to Production Order
8     Activity Consumption to Production Order     No FI Posting
In CO:
Production Order is debited and cost center is credited with activity cost
9     Goods Receipt from Production Order     FG Inventory A/c Dr (BS)
   To COGM A/c Cr (P&L)
10     Delivery to customer     In-Transit A/c   Dr. (BS)
   To FG Inventory A/c Cr (BS)
11     Invoicing to customer     In FI:
Customer A/c Dr (BS)
   To Revenue A/c Cr (P&L)
COGS A/c   Dr (P&L)
    To In-Transit A/c Cr (BS)
In CO:
COGS and Revenue are posted to COPA
     Period end closing u2013 Production Order
12     Revaluation of activity prices     Production Order and Cost Center will be debited or credited as the case may be
13     Calculation of WIP     In FI:
WIP A/c Dr. (BS)
To Change in WIP A/c Cr (P&L)
If the Order is completed:
In FI:
Change in WIP A/c   Dr(P&L)
   To WIP A/c Cr (BS)
14     Calculation of Variances     Variances are Calculated on the Production Order. No FI or CO entries
15     Settlement to Sale Order     Production Order and Sales Order will get debited/credited depending on whether they are positive or negative variances
Period end closing u2013 Sale Order
16     Result analysis at Sale Order     Result Analysis run will identify the status of the sale order and will enable the postings to COPA at the time of settlement
17     Settlement of Sale Order
In FI:
Variances A/c Dr (P&L)
To COGS Account Cr (P&L)
(It would be otherwise if variances are positive)
In CO:
COGS, Revenue and Variances are settled to COPA
SAP Scenario 2 u2013 Non-valuated Sale Order Stock u2013 with Sale Order Controlling
Process Step     Business Process Flow     Value Flow u2013 FI/CO
1     Enquiry
2     Opportunity
3     Quotation (Creation and Approval)
4     Creation of Sale Order
5     MRP Run u2013 Creation of Planned Order u2013 Creation of Production Order and Purchase Order
6     External Procurement u2013 Goods Receipt     In FI:
Consumption A/c   Dr (P&L)
   To GR/IR A/c Cr (P&L)
In CO:
Material costs will directly get posted to Sale Order
7     Material Consumption to Production Order     Not applicable
8     Activity Consumption to Production Order     In FI:
No Entry
In CO:
Activity Costs are posted to Production Order
9     Goods Receipt from Production Order     Only Material Document for movement of goods will be there. The stock is neither valuated in CO nor in FI
10     Delivery to customer     Just goods movement from sale order stock to customer. No value postings in FI and CO
11     Invoicing to customer     In FI:
Customer A/c Dr (BS)
   To Revenue Cr (P&L)
In CO:
COGS and Revenue get posted to Sale Order
     Period end closing u2013 Production Order
12     Revaluation of activity prices     Prodn Order and Cost Center will be debited or credited as the case may be
13     Calculation of WIP     No WIP
14     Calculation of Variances     No Variances
15     Settlement of costs to Sale Order     All the costs accumulated in Production Order gets collected to Sale Order
16     Settlement of Variances     No Variances in Production Order
     Period end closing u2013 Sale Order
17     Result analysis at Sale Order     In FI
WIP A/c Dr. (BS)
To Change in WIP A/c Cr (P&L)
If the Order is completed:
Change in WIP A/c   Dr (P&L)
   To WIP A/c Cr (BS)
No CO postings will happen
18     Settlement of Sale Order     COGS, Revenue and other direct sale order related values will get posed to PA.
Best Regards
Surya

Receiver Determination steps for BPM scenario

Hi Experts,
Scenario : SOAP -> Calling different webservices
1. SOAP Client Request
2. Call the Initial webserive to get the unique Id. No need to pass any request to call this webservice, but it will give the response.
3. Take the Initial websrevice's response as a request to second webservice
4. Pass the SOAP client request to Third webservice
BPM steps
1. Receive Step for SOAP Request
2. Send Step for the Initial webservice call.
3. Transformation step Initial webservice response to request change.
4. Send Step for Second webservice (Pass the the Transformation step's target interface as a request)
5. Send Step for Third webservice ( Pass SOAP client request)
I am done with the BPM flow. Could you please help to do the Receiver Determination steps.
Usually I follow the below steps.
1. Sender Service to BPM
2. BPM to other services. I have a doubt with the second step. I am not passing the SOAP client request to Initial webservice. So, please tell me how to proceed further for the BPM Receiver Determination steps..
Thanks & Regards
Sara

Hey,
First, what is th purpose of your SOAP client request.
Is it just to trigger the BPM.
Second on what basis are you fetching the unique Id from initial web service.
If it is a normal scenario then, the reciever determination will be like this.
Soap client-> BPM
BPM->initial webservice
BPM->second webservice
BPM->third webservice
but in this particular scenario i dont know which data is being used to fetch the unique Id.
regards,
Milan

Need A scenario based step by step process for DTP

Hi BWS,
Can any body give me a scenario based step by step documnet for Data Trasper Process(DTP)..
Cheers
Mak

Hi,
Below is the link for the same. http://help.sap.com/saphelp_nw2004s/helpdata/en/42/f98e07cc483255e10000000a1553f7/frameset.htm
Assign points if this helps.
Regards,
Anil

MORE DETAIL ABOUT MY problem (Configuration Steps for Oracle Forms installation)

OS:WINDOWS 2000 SERVER
DB:8I
FORMS:6I
I WANT TO TEST MY FROM TO RUN ON THE WEB ONLY TEST BY (RUN FROMS IN THE WEB)
BUT I CAN'T DO CONFIGRURATION STEPS (VIRTUAL PATH)
WHERE I CAN DO THIS CONFIGRATION
Configuration Steps for Oracle Forms installation of 06:05:38 2002/10/18
This file gives details of the configuration steps done for you by the installation process
(marked '[INFO]') and of any actions you need to do manually (marked '[ACTION]'). Please read
this file and perform the requested actions.
[ACTION] If you are installing in a new Oracle Home, please reboot the machine after the installation.
[ACTION] Please configure the following virtual path with your web listener: /dev60temp for
physical directory F:\devnt\tools\web60\temp.
[INFO] NT service Oracle Forms Server [Forms60Server] has been created and started for
the Forms Server.
[ACTION] Please configure the following virtual path with your web listener: /forms60java for
physical directory F:\devnt\FORMS60\java.
[ACTION] Please configure the following virtual path with your web listener: /dev60html for
physical directory F:\devnt\tools\web60\html.
[ACTION] Please configure the following virtual path with your web listener: /dev60cgi for
physical directory F:\devnt\tools\web60\cgi.
[INFO] An internet shortcut to run a standard test form, or any form of your choice, has been
created for you in the Oracle Forms program group.
[ACTION] Please configure the following virtual path with your web listener: /jinitiator for
physical directory F:\devnt\JINIT.

Hi Guys,
Any help on this request will be very helpful.
Thanks,
Ashok Kumar.G

MIGO : Detailed steps for doing MIGO.

Hi,
Please help me with detailed steps for doing MIGO for the delivery.
Thanks,
Edited by: hemaraaja on Jul 23, 2008 6:58 AM

Hi,
Enter MIGO in SAP Easy Access screen and press ENTER
Please Ensure Goods Receipt and Purchase order is selected in Drop down Box.
Enter PO number next to PO number drop down box.Also ensure whether 101 movement type in screen right top.
Press enter
In Header,in General Tab ensure document date posting date.
Enter Delivery note number(which will be useful for tracebility)
In Item detail,in Quantity tab enter quantity in unit of entry and in Where tab enter storage location and tick Item OK and click the check button.
If any error found enter the data as shown in error and click check button again and ensure no error messages found.
Then SAVE and note the GRN number in the Delivery paper which received from vendor
reward if useful
Regards

Help in estimating number of dialogue steps for portal user scenarios

I am looking for your expert advice in determining the number of dialogue steps for SAP portal users in the following scenarios:
1) External users accessing a SAP portal to access utilities services such as viewing bills, paying bills, update meter readings etc. The system needs to support 6000 concurrent users.
2) Internal users (customer service agents) accessing IS-U, CRM (potentially BW) via an internal SAP portal. The system needs to support 2000 concurrent users. .
It would be extremely helpful to hear from anyone that has been involved in SAP portal implementations who could advise me on number of dialogue steps to use for each user scenario.
Many thanks,
Celia

I am looking for your expert advice in determining the number of dialogue steps for SAP portal users in the following scenarios:
1) External users accessing a SAP portal to access utilities services such as viewing bills, paying bills, update meter readings etc. The system needs to support 6000 concurrent users.
2) Internal users (customer service agents) accessing IS-U, CRM (potentially BW) via an internal SAP portal. The system needs to support 2000 concurrent users. .
It would be extremely helpful to hear from anyone that has been involved in SAP portal implementations who could advise me on number of dialogue steps to use for each user scenario.
Many thanks,
Celia

Detailed steps for migrating standard buisness content

Hi,
Please provide me the detailed steps for migrating existing 3.5 standard business content datasources to 7.0 version
Thanks in advance

ECC - RSDS - Give Datasource - Menu - Migrate
<b>* Do it with export</b>
Message was edited by:
Jr Roberto

Need Message Type Creation Steps for Different Scenarios

Hi Friends,
I have done following steps for Outbound IDoc [Extended IDoc]
1. Create custom Message Type                           WE81
2. Create custom Segments               WE31
3. Create IDoc Extension               WE30
4. Create IDoc Type [Basic+Extu2019n]          WE30
5. Link Custom IDoc with Message Type          WE82
6. Activate CP for Custom Message Type                     BD50
7. Activate Change Pointers globally Flag on     BD61
8. Maintain custom message type in CDM                     BD64
9. Define partner profile for custom msgtype                    WE20
After completion of the above steps.
I am unable to do the following steps.
10. Checking the IDoc Creation                          BD10
          or
11. Execute CP IDoc generation Program     RBDMIDOC
Here these steps I am unable to find Message Type.
If we create message type thru BD53 [std idoc] it will come.
but my situation is for extended IDoc I need to create message type.
If any one worked on this situation Help me out.
Regards,
Mutyapu4u.
Edited by: naveen mutyapu on Jun 24, 2008 2:51 PM

Hi,
Check the link below:
http://www.****************/Tutorials/ALE/ALEMainPage.htm
Hope this helps..
Regards,
Sharath

Steps for Email integration in sap crm system?

Hi Experts,
Please guide me the steps for email integration so that the emails are in syn with the WEB UI Interaction centre.Settings at the backend GUI are already defined.Actually in my case the Development system is not integrated with Email sync in WEB UI.I need to test the email functionality in Development system as steps I have followed are as below:
1)TCode :- SBWP,then I have created a mail & send it to email address which is defined in the SO28
2)TCode :- SOST,there I have clicked on my test mail,select it & click on execute button,green light appears & shows the message that the email is successfully forwarded.
Now when I open Web Ui,select my business role & then I go to inbox in the Navigation Bar,select email & click on search.Then it does not appear anything & shows search result zero.
Kindly suggest me the steps so that I can see my test email in Dev system Web Ui business role .
Thanks
Warm Regards
Vineet Joshi

Hi Prashant,
Thanks for your response. I want steps to configure communication channels like e-mail & fax to facilitate receipt of invoice from vendors, sending of PO to vendors, cheques, payment advices to name a few. Please let me know the detailed configuration steps for the same and also do we need to instal any tool to facilitate this process.
Thanks
Best regards,
Bhaskar
Edited by: Bhaskar Umashankar on Nov 25, 2008 4:08 AM
Edited by: Bhaskar Umashankar on Nov 25, 2008 4:08 AM

Steps for Idoc to EDI Subsystem

Hi all,
Can anyone tell me the steps that i have to worry about to send an idoc immediately to EDI Subsystem
I mean what all things i have to specify while creating ports and partner profiles etc
Thanks

Sending Order Confirmations by EDI (SD-SLS)
Use
By setting up and using the Electronic Data Interchange functions in the R/3 System, you eliminate the need to print documents and send them through the standard mail system. Instead, you send the information electronically. This method is more practical, convenient, and allows you and your customer to process data faster.
In this EDI scenario, you process and send order confirmations to a customer's R/3 Purchasing system.
Prerequisites
Application
Customizing
To process outbound order confirmations, you need to make all of the necessary EDI settings in Customizing for Basis. You make settings for output control in Customizing for Sales and Distribution.
Output Control
The standard SD condition components are:
Condition component     Value
Sales document type     AA
Output determination procedure     V10000
Condition type     BA00
Transmission medium     6 (EDI)
Access sequence     0001
Processing subroutine     Program RSNASTED, form routine EDI_PROCESSING
Partner function     SP (sold-to party)
Application     V1
Condition records for outbound order confirmations are maintained in Customizing for Sales and Distribution. Choose Basic Functions  Output Control  Output Determination  Output Determination Using the Condition Technique  Maintain Output Determination for Sales Documents.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data for the outbound parameters for partner profiles and the additional profiles for message control:
Field     Value
Message type     ORDRSP
Partner type     KU (customer)
Partner function     SP (sold-to party)
Receiver port     e.g. SUBSYSTEM
Output mode     e.g. Transfer IDoc immediately
Basic type     ORDERS04
Process code     SD10
Activities
Create an order. When you save the document, the system uses your settings in output control to find the appropriate condition record and send confirmation of the order by EDI. To review and maintain output data in the document, choose Extras  Output  Header.
Receiving Acknowledgments via EDI (MM-PUR-GF-CON)
Use
You have arranged with your vendor that that latter is to send you acknowledgments in respect of purchase orders or outline agreements received from your company. (Note: both kinds of acknowledgment are generally referred to as "order acknowledgments" in the system. The corresponding EDIFACT term is "order response" (ORDRSP).)
You have the option of working exclusively with acknowledgments. The acknowledgment is then purely informative in nature, since only the acknowledgment number is recorded in the system.
If you wish to receive different kinds of vendor confirmation, such as both order acknowledgments and shipping notifications (also known as advance shipping notices - ASNs), it is possible for quantities and dates to be entered in the system automatically).
For more information on this topic, refer to the MM Purchasing documentation ( Confirmations from the Purchasing Viewpoint and Receiving Confirmations via EDI).
Prerequisites
Application
To work with several categories of vendor confirmation, you must:
u2022     Enter a confirmation control key on the item detail screen
u2022     Set up the confirmation control facility in Customizing for Purchasing (Purchasing  Confirmations  Set up Confirmation Control). There you can specify the order in which you expect confirmations from your vendors, for example.
Under Confirmation sequence, you can:
u2022     Specify tolerances for date and price checks
u2022     Allow vendor material changes (VMat indicator)
u2022     Adopt vendor price changes (Price indicator)
Do not use a confirmation control key if you work exclusively with acknowledgments.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  EDI  Set up Partner Profile):
Parameters for Inbound Messages
Field     Value
Partner type     LI
Partner role     LF
Message category     ORDRSP
Process code     ORDR
Processing     Initiate immediately or process via background program
Activities
When an acknowledgment is received in the form of an incoming EDI message, the system checks whether a confirmation control key has been entered in the relevant PO or outline purchase agreement.
u2022     If there is no confirmation control key, only the acknowledgment number is entered on the item detail screen.
u2022     If there is a confirmation control key, the system updates the confirmation overview. That is to say, the dates and quantities set out in the acknowledgment that has just been received are recorded and taken into account in the overview. To view acknowledgments that have been received, choose Item  Confirmations  Overview from the item overview. Column C (creation indicator) contains the value 3, meaning that the acknowledgment was received via EDI. The system also enters the IDoc number in the External document column.
An IDoc can always acknowledge one purchase order only. The acknowledgment relates to the PO item, not to any individual schedule lines.
Exceptions
When an acknowledgment is received via EDI, the system automatically checks quantities, prices, and dates. In checking quantities, it applies the over- and underdelivery tolerances set for the item. You can set tolerances for prices and delivery dates in Customizing for Purchasing under Set up Confirmation Control.
The tolerances you define apply to all vendors. Using the enhancement MM06E001 provided by SAP, you can specify that the tolerances do not apply to certain vendors.
If the acknowledged quantities, prices, and dates vary from those set out in the PO or purchase agreement, the system issues a warning message. In this case, the purchasing document is not updated.
For more information on this topic, refer to the section Error Correction (Receiving Confirmations via EDI) of the MM Purchasing documentation.
Sending PO Change Notices via EDI (MM-PUR-PO)
Use
This section describes how to transmit a change notice relating to a purchase order that has already been sent to a vendor.
The function corresponds to the transmission of a purchase order via EDI.
Prerequisites
Application
You have already successfully transmitted the original purchase order to the vendor via EDI.
Message Control
You have created message condition records for your EDI vendors (Purchasing  Master data  Messages  Purchase order  Create).
Use the message type NEU to transmit PO change notices.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  Set up Partner Profile):
Parameters for Outbound Messages
Field     Value
Application     EF ( Purchasing: purchase order)
Message category     ORDCHG
IDoc type     ORDERS02 or ORDERS04
Process code     ME 11 (ORDCHG: PO change notice)
If you wish to transmit PO conditions or texts to your vendor, you must create an IDoc view. For more information on this topic, see Sending a Purchase Order via EDI.
Activities
Change an existing purchase order via Purchasing  Purchase order  Change. Make the necessary changes and save the PO.
The new message is compared with the last successfully transmitted message. PO change notices indicate whether any new items have been added to the PO, and/or whether any already transmitted items have been changed.
When the message is transmitted, only those changes that are simultaneously new and print-relevant are included. The system sets the change indicator for the new message. To check the change indicator, choose Header  Messages in the PO item overview.
See also:
MM Purchasing: Creating a Purchase Order
Cross-Application Components: Customizing Message Control in Purchasing (MM): Example: Purchase Order
Receiving Order Changes by EDI (SD-SLS)
Use
In this EDI scenario, you receive and process order changes sent by a customer from an R/3 Purchasing system.
Prerequisites
Application
General
You can receive and process order changes in your system only on the basis of an existing order.
Customizing
To process incoming order changes, you need to make all of the necessary settings in Customizing for Basis. There are no special settings for Sales and Distribution.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data in the header and detail screen for inbound parameters:
Parameter     Value
Partner type     KU (customer); if the IDoc is sent from an R/3 system via tRFC (in a typical case with ALE scenarios), enter LS for logical system!
Message type     ORDCHG
Process code     ORDC
Processing     Process immediately
Allowed Agents     Enter an R/3 user or an organizational unit, for example.
Activities
Inbound Processing
The IDoc interface receives the IDoc and reviews its control record. According to this record and the corresponding partner profile, the IDoc is transferred to the function module IDOC_INPUT_ORDCHG in Sales and Distribution. The ALE services are called.
The system processes the IDoc in the background, using the data records in the IDoc to determine the relevant order.
If processing is successful, the system updates the sales order. The IDoc is sent back to the IDoc interface which updates the status records in the IDoc.
Exception Handling
If it cannot determine an order, or if an error occurs in processing, the system determines the relevant agent(s) and sends a workitem to the integrated inbox(es). An agent can pick up the workitem to process the IDoc or simply end processing.
To display an IDoc for order changes, choose Environment  Display facsimiles in the order. The system displays a dialog box of object links where you can choose Linked IDocs.

Details scenario navigation steps for async_sync bridge for bapi_po_create

Similar Messages

Maybe you are looking for