LSMW idoc Inbound Processing settings

Hi,
We have done LSMW with BAPI method to create Bank master.
In Idoc Inbound Processing settings -
We created partner type as 'B' i.e, for BANK
While creating Partner Number it is not allowing to create Partner Number. The error is  "Enter a permissible partner number"
Please let me know what would be the problem.
Regards,
Hari
Edited by: Bhatlapenumarthy Hari Krishna on Sep 12, 2008 9:31 AM

Hi,
Use patner type as US only and LSMW as Patner number.
this will surely solve your problem .
plz do this way :
The first requirement is a file port for the file transfer. If required, create a port of the file type via Maintain ports. To do this, position the cursor on "File" and press Create. You should be in change mode. SAP recommends:
Port: LSMW
Name: Legacy System Migration Workbench
Version: 3 (IDoc record types SAP Release 4.x)
Outbound file Please enter a (dummy) physical directory and a file name, i.e. u2018filelsmwu2019 ·
As an addition, you can specify a tRFC port. This port is required, if you do not want to create a file during data conversion but submit the data in packages directly to function module IDoc_Inbound_Asynchronous.
SAP recommends:
Port: assigned by the system
Version: 3 (IDoc record types SAP Release 4.x)
RFC destination: Name of R/3 System
Name of port: Legacy System Migration Workbench.
Then the partner type should be defined or selected. SAP recommends:
Partner type: "US" (User)
As of release 4.5A, this partner type is available in the standard system. Up to release 4.0B inclusive, this partner type is not available in the standard program and should be added. SAP recommends:
Partner type: Create US
Report name: /SAPDMC/SAP_LSMW_PARTNERTYPES
Form routine: READ_USER
Short description: any.
Finally a partner number should be defined or selected. SAP recommends:
Partner number: LSMW
Partner type: US
Partner status: A (active)
Type: US
Language: DE or EN
Person in charge: Your user ID.
Activate IDoc inbound processing
reference : help.sap
thanx.
Edited by: Dhanashri Pawar on Sep 12, 2008 7:10 AM

Similar Messages

  • Error : Pre Settings for IDoc inbound processing are missing error

    Hi Experts,
    There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
    Thanks in advance.
    Madhurima.

    I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
    [iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

  • Activate IDoc Inbound Processing in LSMW

    Hi Gurus,
    Why do we need to activate the IDoc Inbound Processing in LSMW if we are going to use BAPI or IDoc in LSMW?
    Thanks and Regards,

    Hello Paulo
    Recently I implemented an ALE scenario where the sending and receiving logical system are the same.
    Purchase orders are sent to SAP-XI which returns the IDoc to the same logical system als sales order IDoc.
    Thus, our logical system has the ORDERS message type as outbound and inbound parameter. SAP-XI is the other receiving and sending logical system.
    The easies way is the "Copy&Paste" approach. Look into your system for existing inbound IDocs and compare their control record with the one of your test IDoc.
    Regards
      Uwe

  • ALE IDOC Inbound processing using IDOC_INPUT_ORDERS

    Hi experts,
    I am stuck up with IDOC inbound processing.
    Can you please let me know about the process in Receiving Purchase Order from the customer system and creating Sales Order in the SAP system? using FM IDOC_INPUT_ORDERS. I have an Idea about WE20, NACE etc.
    Can you please explain me about the process on how to go about it?
    Kind regards,
    Shiva.

    Hi,
    I have moved this thread from [ABAP, General Forum |ABAP Development; to [Data Transfers Forum|ABAP Connectivity;.
    The forum Data Transfer is the place to discuss LSMW, ALE, BDC, Data Transfer Techniques, Batch Data Communication, Legacy System Migration Workbench, Application Link Enabling, IDOCs, BAPIs.
    Please, the next time check the most appropriated forum category before posting. Thus you have more chance to have your question answered !
    Best Regards.
    Marcelo Ramos

  • IDoc Inbound Processing for CREMDM & DEBMDM

    Hi experts,
    I'd like to gather some feedback from you regarding the topic ERP IDoc Inbound Processing for CREMDM & DEBMDM. As you all know, there's currently no option to directly process CREMDM/DEBMDM IDocs in ERP. Currently you have to use PI for splitting the CREMDM/DEBMDM message into its related ADRMAS and CREMAS/DEBMAS IDocs.
    My areas of interest are:
    1) How satisfied are you with the current situation? Does the split work? Are there issues or problems in the current message handling? What are the Pro's and Con's from your point of view?
    2) What would be the requirements for a CREMDM/DEBMDM handler? What would you expect? Maybe you have implemented  something similar on project basis and could post some feedback?
    One painpoint I'd see with a CREMDM/DEBMDM inbound is that you'll lose the IDoc Monitoring capabilities. The message split allows a single record tracing in the IDoc Monitor (as there is a 1:1 relation between IDocs and records). This changes for the mass processing. The monitor would display only the status of the IDoc and you'd need some other monitoring capabilities to check the results on record level. What are your thoughts about that? Is the monitoring important? Would the application log be a feasible solution for that challenge?
    Additional comments are welcome, of course.
    Best regards
    Michael
    PS: @ Matt, please contact me by mail. thanks.

    Hello ,
    Here are some other pain areas regarding the message split :
    1. Complicated monitoring proess & reprocessing error idocs : We have to monitor ADRMAS & CREMAS or ADRMAS & DEBMAS during inbound processing. Also we could not find any best practices to reprocess error idocs. E.g. If ADRMAS fails & CREMAS succeeds what is the impact . Also the impact if it is reveresed. We know for sure that if CREMAS fails , vendor will not be created / updated. But we could not find specific pointers for ADRMAS failures.
    2. It is a tedious process to link CREMAS with corresponding ADRMAS idoc specially when SAP maintains internal number range for vendors.
    3 . The process is complicated if you are managing customer or vendor contact information with contact address . We could succesfully implement the integration but it took us a while to reach end-point.
    4. Splitting really does not seem to support if ERP maintains internal number range.
    5. Another major issue we observed is , if ADRMAS is under process & corresponding DEBMAS or CREMAS is posted , it fails raising the message that Account is locked. Default serialization does work in ERP system . But overlap of few microseconds also cause this error.
    Hope this helps !!
    Please let me know if you need any other specific details since we have used MDM - ECC integration using PI to its maximum extent .
    Regards
    Yogesh

  • What is IDOC Inbound process and Outbound Process?

    What is IDOC Inbound process and Outbound Process?
    can any one explain about the inbound and outbound process step by step?
    Tks in advance,
    Phanikumar

    Hi,
       Inbound means transfer legacy data to SAP system and
      outbound means transfer SAP system data to legacy system.
    Regards,
    Prashant

  • Idoc inbound processing? from non-sap system?

    Hi experts,
    I'm confused with some functions below:
    IDOC_INBOUND_SYNCHRONOUS
    INBOUND_IDOC_PROCESS
    IDOC_INBOUND_SINGLE
    IDOC_INBOUND_ASYNCHRONOUS
    can you tell me what are the differences? when to use them?
    for sap outbound processing, we can only call function master_idoc_distribute to generate idoc or use message control to trigger outbound idoc. no other options, correct?
    for sap inbound processing, if we use message control for automatical posting, we have process code which read  the inbound idoc file and do the sap posting. when to use those functions above?
    does the middlewares like seeburger, GIS call those functions to generate idocs at SAP side?
    in what scenarios can we use those functions? read directly non-sap file into sap internal table then call the functions to create inbound idoc? how about the posting? call inbound processe code function after the functions above?
    in case the interface between sap and legacy system is using above functions to build inbound idoc in sap and sap use process code for inbound posing, sap can monitor all inbound process using idoc, but how can the legacy system mornitor the interface?
    Thanks.
    Legend.
    Edited by: legend li on Dec 21, 2010 4:58 PM
    Edited by: legend li on Dec 21, 2010 5:40 PM

    Hi Christophe,
    Awesome!!!!!! it worked, You are the best.
    I could able to create a sales order in CRM,but below are the valid data I passed in the respective segment fields.Except for first 3 values rest all did not get reflected in teh Sales order.I feel i am missing some qualifiers.
    Can you kindly share the  IDoc data to be passed in...along with respective segments and fields:
    Segment                                                 Field
    E101CRMXIF_BUSTRANS     OBJECT_TASK         
    E101CRMXIF_BUSTRANS     PROCESS_TYPE
    E101CRMXIF_BUSTRANS     POSTING_DATE
    E101CRMXIF_PARTNER                          PARTNER_NO
    E101CRMXIF_PARTNER                RELATION_PARTNER_NO
    E101CRMXIF_ORGMAN         SALES_ORG
    E101CRMXIF_ORGMAN          DIS_CHANNEL
    E101CRMXIF_ORGMAN         DIVISION
    E101CRMXIF_SALES             PO_NUMBER_SOLD
    E101CRMXIF_SALES            YOUR_REF_SOLD
    E101CRMXIF_SALES            PO_NUMBER_SHIP
    E101CRMXIF_BUSTRANS_ITEM     ITEM_NUMBER
    E101CRMXIF_BUSTRANS_ITEM     ITEM_TYPE
    E101CRMXIF_BUSTRANS_ITEM     ORDERED_PRODUCT
    E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT
    E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT_ISO
    E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT
    E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT_ISO
    E101CRMXIF_SCHEDLIN_I     ORDER_QTY
    Thanks a ton in advance .
    Vijay

  • IDOC inbound processing ( Function module Rquired )

    Hi,
    I am working on IDOC inbound, I am looking for a standard FM for Production order confirmation which i need to assign in WE57 along with the standard Message type(Production order confirmation).
    Could you please let me know where i can get the standard inbound function modules for the standard idoc types,
    for eg: IDOC_INPUT_ORDERS for sales order.
    Thanks.
    Krishnakumar

    Hi,
    Go to WE42 for inbound processing codes and WE41 for outbound.
    OR
    We  have WE19 which is a test tool for IDOC processing.
    Provide the IDOC number  then press F8, then in the next screen , you will have inbound function module.
    Click that  button. Then enter the text in search criteria.
    Then you can get related function module.
    Reward points if helpful.
    Thanks and Regards

  • IDOC Inbound Processing and updating DN

    Hi,
    I'm unfamiliar to inbound processing (i just understand the basics). I've dealt with outbound processing and user exits associated with that.
    I have a specific client requirement: an Inbound IDOC is to be processed and update a delivery note. Some field of some segment within this inbound idoc will carry some information which I need to extract and update a field  in the Delivery Note with. How could I do this?
    Inbound message type is DESADV. Does my requirement need user exit programming or can I set up some kind of a batch job process?
    Thanks in advance,
    Risad

    HI,
    For processing inbound idoc one process code attached in the partner profile. From this process code you can find out the function module attached to it.
    Inside function module use can check for exit or badi to modify DN or write your custom logic. If you already have the test data you can check it from we19. Here you need to select standard inbound.
    Thanks
    Subhankar

  • Test IDOC inbound processing in WE19

    Hello,
    I want to test an inbound processing for an IDOC in WE19. I don't have any message so i enter 'via message type' in the initial screen.
    Then i fill the segments/fields of the presented segments that i think are necessary and also some data in the 'Edit control record fields'.
    But when i click on button 'Standard inbound' i receive the error message 'Initial recipient partner type'. Please note I don't fill any parameter in the control fields for receiver, but even if I enter a value in 'partner type' for receiver I got the same error. If I need to fill this parameter I don't know what should it contains.
    Does anyone have an idea about what could be the reason of this error ?
    Thanks is advance,
    Paulo Sousa

    Hello Paulo
    Recently I implemented an ALE scenario where the sending and receiving logical system are the same.
    Purchase orders are sent to SAP-XI which returns the IDoc to the same logical system als sales order IDoc.
    Thus, our logical system has the ORDERS message type as outbound and inbound parameter. SAP-XI is the other receiving and sending logical system.
    The easies way is the "Copy&Paste" approach. Look into your system for existing inbound IDocs and compare their control record with the one of your test IDoc.
    Regards
      Uwe

  • Idoc inbound process

    HI
    IDocs can be passed to the application either immediately on arrival or can follow in batch.
    I can post an inbound IDoc by calling a function module directly: A function is called that imports the IDoc directly.
    Can anyone tell how to do this which function module i have to choose and how to create process code for inbound process?
    thanks

    Hi,
    If you are using your own Z function module
    create that entries for you FM using the BD51 else if you are using
    idoc_input_matmas01 which is sap provide which you can already exist in this list
    if you run BD51.
    Now go to WE57 and assign the Direction as '2' ( For Inbound processing)
    Basic TYpe , Message type and If you have Mess code also then also assign here.
    Now go to WE42 ( For Process Code ) create new entires for Process code
    in Identification assign your FM.
    Now go to WE20 and selct tyour Partner type and
    on the left side of screen you will se Inbound parameters there create the enteris
    and assign the Process code.
    thanks
    PK

  • LSMW and IDoc Inbound processing?

    Hi,
    I am having a query in data bulk upload.COuld any one help me out.
    Regards,
    John.

    John,
    My collegue has written a good blog on this. You could have a look /people/hema.rao/blog/2006/09/14/lsmw--step-by-step
    ~thomas

  • Idoc inbound processing - Combine process codes

    Hello,
    i have the following problem. I receive an idoc from system a) and i want to process the idoc in the HR system and afterwards I want to forward the idoc to System B).
    If i use HRMD as process code for in the partner profile on the HR system - the idoc which contains an user id is processed but not forwarded.
    If i use ED08 as process code instead of HRMD the Idoc is forwarded but not processed.
    But i need both - is there a possibility to combine two process codes although one is only a function module ant the other one is a workflow?
    It would be great if anyone can help me.
    Best regards
    Ariane

    Hi,
    a function module was created and that works out well as long as one idoc contains only one E1PLOGI segment.
    System A sends the Idocs due to change pointers. Is there a chance to do settings so that only one employee is distributed per idoc?
    Thanks a lot in advance

  • Contractor idoc inbound processing

    Hi,
    Cabn anyone please explain me how to process inbound idoc for purchasing contractor?
    thanks,
    raghav

    Hi,
    Cabn anyone please explain me how to process inbound idoc for purchasing contractor?
    thanks,
    raghav

  • IDoc Inbound Process: to do Results Recording via QE51

    Requirements:
    IDocs will send from external system, including Plant, Material, Batch, Storage Location, Charateristic. We want to read these IDocs, according the fields value to find the Inspection Lot of the specify Characteristic via QE51, then do the results recording.
    Would you pls guide me how to realize this process step by step? How to config the scenario, EDI, IDoc and Program?
    Thanks.

    Hi ,
              Please check out the below procedure .
    MESSAGE CONTROL (USING EDI / ALE)
    For Purchase order (Message control using EDI and message type ORDERS) – STEPS
    Settings to be done in the Sending system
    From NACE
    Choose Application – EF ( Purchase order), press on condition record
    Output type – NEU – Purchase order / double click ;choose  Purchasing output determination:Doc type/purc org/vendor . Key in the data (Purchasing doc type – NB, Purc organisation – 0001, Venor – vendor11) execute. Key in the data (vendor –vendor11, name – name1, partner function  - VN, Partner – Vendor11,Medium – 6 (EDI), time – 4(send immediately), language – EN).
    Press on output types , choose NEU –Purchase order, double click,  Access sequence 0001(doctype/purcorg/vendor) tick mark the access to condition, go to default values (dispatch time – send immediately, Transmission medium – EDI, Partner function –VN)
    Create RFC destination from SM59 (ZNARA_ALE_EDI).
    Create a port from ZNARA_ALE.
    Create partner profile vendor11 under LI and not LS. PARTNER NUMBER SHOULD BE  SAME AS THAT OF VENDOR SET IN THE CONDITION TYPE.
    In the outbond parameters of the partner profile Vendor11 key in the data (Reciever port -> ZNARA_ALE,
    Basic type –ORDERS05, Message type – ORDERS ) Go to the message control and key in the data (Application – EF, Message type – NEU, Process code –ME10, Transfer immediately )
    Create a purchase order from ME21 with data (Purchasing doc type – NB, Purc organisation – 0001, Venor – vendor11). System will generate an outbond Idoc automatically which can be seen from WE02.
    For Purchase order (Message control using ALE and Message type ORDERS) - STEPS
    To transfer the idoc from Client 555 to 500
    Settings do be done in 555.
    From NACE
    Choose Application – EF – Purchase order, press on condition record
    Output type – NEU – Purchase order / double click ;choose  Purchasing output determination:Doc type/purc org/vendor . Key in the data (Purchasing doc type – NB, Purc organisation – 0001, Venor – vendor11) execute. Key in the data (vendor –vendor11, name – name1, partner function  - VN, Partner – Vendor11,Medium – A (ALE), time – 4(send immediately), language – EN).
    Press on output types , choose NEU –Purchase order, double click,  Access sequence 0001(doctype/purcorg/vendor) tick mark the access to condition, go to default values (dispatch time – send immediately, Transmission medium – ALE, Partner function –VN)
    From SALE create two logical systems and assign them to the respective clients (ZALERECV_N – 500, ZALESEND_N – 555).
    From SM59 create RFC destination with the same name as that of the receiving logical system  (ZALERECV_N).
    From BD 64(distribution model),  create a model view with Technical name ZNARA_PO (message type – ORDERS, Sender – ZALESEND_N, Receiver – ZALERECV_N). Generate partner profiles. Distribute.
    Note that partner profile will be generated under LS.
    Settings do be done in 500.
    From NACE create two logical systems and assign them to the respective clients (ZALERECV_N – 500, ZALESEND_N – 555).
    From BD 64(distribution model), keep the cursor on Technical name ZNARA_PO. Generate partner profiles. Note that partner profile will be generated under LS. Change the process code to ORDE in the inbond parameters .
    Now in client 555, Create a purchase order from ME21 with data (Purchasing doc type – NB, Purc organisation – 0001, Venor – vendor11). System will generate an outbond Idoc automatically which can be seen from WE02. The purchase order details will be updated in 555 thru the inbond idoc.
    IMP data for message control in  Sales order creation.
    Partner profile to be created under KU.
    Outbond parameters in the partner profile (Message type – ORDRSP, Basic type – ORDERS02, partner profile - SP) In Message control (Application – V1, Message type – BA00, Process code – SD10)
    Notes:
    Check the entries in the NAST table to see whether outbond idoc has been created successfully or not
    If you have choosen collect idocs in the partner profile, use trans code BD87 to process them
    Table EDP13 - Partner Profile: Outbound (technical parameters)
    Table EDP21 - Partner Profile: Inbond (technical parameters)
    Please reward if useful.

Maybe you are looking for