Distribution of WBS with ALE

Hi - Currently, we have ALE setup & tested for message type: MATMAS,CLSMAS, CHRMAS, KNOMAS (Material, Class, Characteristics & Dependency)between two clients. To add WBS (Work Breakdown Structure) into this ALE process, what addition configuration is required? For example, what's the message type to add for this in BD64. From this doc http://help.sap.com/saphelp_46c/helpdata/en/35/6f2986268b2239e10000009b38f984/frameset.htm
I'm not able to find which filter or where to insert values below under according to the doc:
Object name: WorkBreakdownStructure
Method: SaveReplica
Thanks -
Kalven

Hi,
While inisde your distribution model in BD64, switch to change mode, select your model, and press the button to Add BAPI (Ctrl+F6). There you can enter mentioned object name and method name.
Regards

Similar Messages

  • Data migration with ALE/Idoc

    Hello .
    I want to migrate data between two SAP system using ALE / IDOC, and I want to know the settings to make on each system (source and target).
    Does someone has an idea?
    Thank you all

    Outbound Settings
    Define Logical Systems and Assign Client to Logical System u2013 Transaction SALE
    u2022     Go to Define Logical System (See the figure)
    u2022     Define a new logical system to identify the local system and save it
    u2022     Now, go to Assign Client to Logical System (See the figure)
    u2022     Add a new entry
    u2022     Specify the client, previously created logical system and other attributes
    u2022     Save the entry
    u2022     Define a new logical system to identify the partner system and save it
    Maintain RFC Destinations u2013 Transaction SM59
    u2022     Create a new RFC destination for R/3 type connection
    u2022     Specify the target host on Technical settings tab
    u2022     Provide the Logon credentials on the Logon/Security tab
    u2022     Save the settings
    u2022     To verify the settings, Click on Test connection or Remote logon
    Define Ports u2013 Transaction WE21
    u2022     We need to define a tRFC port for the partner system
    u2022     Click on Transactional RFC node
    u2022     Create a new port
    u2022     Provide a description
    u2022     Specify the name of the target RFC destination
    u2022     Save the object
    Maintain Distribution Model u2013 Transaction BD64
    u2022     Click on Change
    u2022     Create a new model view
    u2022     Provide a Short text and Technical name to the model view
    u2022     Add message type
    u2022     Specify sender and receiver systems
    u2022     Also, specify the message type that we created previously
    u2022     Save the Distribution model
    Generate/Create Partner Profile u2013 Transactions BD82/WE20
    u2022     To generate Partner profiles automatically you may use BD82 or go to BD64 and use the menu path Environment -> Generate partner profiles
    o     Otherwise, you may use transaction WE20 to create a partner profile
    u2022     On selection screen, specify the model view, target system and execute
    u2022     The result log will be displayed on the next screen
    u2022     To verify the partner profile go to WE20
    u2022     Check the partner profile for the target system
    Distribute Model View u2013 Transaction BD64
    u2022     Select the Model View
    u2022     Go to menu path Edit -> Model View -> Distribute
    u2022     Result log will be displayed on the next screen
    Inbound Settings
    u2022     Define Logical Systems u2013 Transaction SALE (Please refer to Outbound Settings discussed)
    u2022     Assign Client to Logical System u2013 Transaction SALE (Please refer to Outbound Settings discussed)
    u2022     Maintain RFC Destinations u2013 Transaction SM59 (Please refer to Outbound Settings discussed)
    u2022     Define Ports u2013 Transaction WE21 (Please refer to Outbound Settings discussed)
    u2022     Generate/Create Partner Profile u2013 Transactions BD82/WE20 (Please refer to Outbound Settings discussed)
    u2022     Assign Function Module to Logical message u2013 Transaction WE57
    o     Create a new entry
    o     Specify name of the Function Module
    o     Also, specify Type as F, Basic IDoc type , Message type  and Direction as 2 (Inbound)
    o     Save the entry
    u2022     Define Input method for Inbound Function Module u2013 Transaction BD51
    o     Create a new entry
    o     Provide Function Module name 
    o     Specify the Input method as 2
    o     Save the entry
    u2022     Create a Process Code u2013 Transaction WE42
    o     Create a new Process Code
    o     Select Processing with ALE Service
    o     Choose Processing type as Processing by function module
    o     Save the entry
    o     On the next screen, select your function module from the list
    o     Save the changes
    o     Now you will be taken to the next screen
    o     Double-click on Logical message
    o     In the Assignment to logical message, specify the message type
    o     Save the changes

  • File to convert to IDOC from bus.service failes with ALE#LI

    Hello,
    we habe implemented a scenario:
    Non SAP system sends a structure to be uploaded to an R/3 system as IDOC.
    All config looks fine.
    We followed this description:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    So system is identified in adapter specific data as log.sys. LS test1 .
    But we have this error:
    Unable to convert partner abc / ALE#LI into an IDOC partner (message in german, only translated)!
    Does anybody has an idea what is wrong?
    Is it necessary to have the log.sys name in the message e.g. in SNDPRN?
    Here we have after mapping:
      <SNDPOR>testABC</SNDPOR>
      <SNDPRT>LI</SNDPRT>
    Best regards
    Dirk
    Message was edited by: Dirk Meinhard
    Message was edited by: Dirk Meinhard

    Hi Nimrod,
    looks like I am not totally wrong here, but working together with externals who provide the outbound side is not really easy for testing.
    Here is the EDI_DC-40 segment AFTER the Mapping, so the XML for the inbound IDOC:
    - <PORDCR05>
    - <IDOC BEGIN="1">
    - <EDI_DC40 SEGMENT="1">
      <TABNAM>EDI_DC40</TABNAM>
      <MANDT>010</MANDT>
      <DIRECT>1</DIRECT>
      <IDOCTYP>PORDCR05</IDOCTYP>
      <MESTYP>PORDCR</MESTYP>
      <SNDPOR>A000000039</SNDPOR>
      <SNDPRT>LI</SNDPRT>
      <SNDPRN>0005354880</SNDPRN>
      <RCVPOR>SAPK10</RCVPOR>
      <RCVPRT>LS</RCVPRT>
      <RCVPRN>LOG10</RCVPRN>
      </EDI_DC40>
    Here is the error message:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Aufruf eines Adapters
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY</SAP:Code>
      <SAP:P1>Partner_ABC</SAP:P1>
      <SAP:P2>ALE#LI</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Sender XI Party Partner_ABC / ALE#LI / could not be converted to IDoc Partner </SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    In my opinion we have to implement in WE20 of receiver R/3 system a partner LI with this number A000000039 from the EDI DC 40 segment? And we need to add it as identifier LOGICAL with ALE#LI and this number A000000039.
    R/3 consultant says he cannot do this in the receiver R/3 system because the sender is no supplier in his system!
    regards
    Dirk

  • How to start with ALE and Idocs

    Hi,
    I want to start with ALE/Idocs, Could you please guide me from where should I get the docs for that.
    A lot of thanks in Advance

    Hi Nitin ,
    Pls go through the book by Arvind Nagpal , one of the best books that no one should miss.
    Have a look at this site as well
    http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-part-iii/
    Check this thread, where you have step by step creation of IDOCs:
    idocs
    Check these links, where you get the complete information on IDOCs:
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    Regards,
    Vvieks

  • Can we go with ALE configuration instead of receiver idoc adapter at target

    Hi Experts,
    Could you please provide me some idea when why don't we go with ALE configuration to exchange IDOC from PI  to Target system instead of configuring receiver IDOC adapter at target side.

    Hi Raj
    Point 1:
    When we send IDoc from SAP system to PI ,it used ALE connections nothing but using RFC destination and Port it establishes the connection IDoc will reach PI ABAP Stack.
    Point 2:
    When we send IDoc to ECC using PI IDoc adapter it uses the same mechanism(RFC destination/Port),but the only purpose of IDoc comm8unication channel is to call RFCDEstination and Port created in PI.
    i.e: There is no difference in communication(Point 1 and Point 2) both uses TRFC calls.
    Regards,
    Raj

  • HTTPS with ALE

    Can we use HTTPS with ALE to establish a connection between the HR and ERP system?  There are seperate instances for FI and HCM and we require an ALE interface between them.  RFC with SNC is not an option so am wondering if there is an ALE with HTTPS route we can take?  Any info will be greatly appreciated.

    Hi Fahad,
    As far i know there is no way to using https for ALE without PI. because ALE is base on RFC technology not http / https.
    if my knowledge correct then you might need to use other middleware like SAP PI, webMethods, Tipco etc or if not you might need to do some customize scenario using webservices. but both of your ERP and HCM must be at least ECC 6.
    for IDOC for example you can set the port to generate xml file. and create program to pickup and send it over soap https to HCM system.
    Please correct me if i am wrong.
    Regards
    Fernand.

  • Settlement of WBS with Partially Released status

    Hi colleagues,
    We are encountering problems during our settlement to AUC. Although the settlement rule is maintained, the system does not allow us to post the settlement to a WBS with "PREL" (partially released) status. Is this really the standard of the system? When can we release the WBS?
    Thank you.

    Ask your FICO consultants to create a separate Asset class for AUCs.
    They can maintain such class in OAOA, where ask them to maintain status of Auc as Investment Measure.
    Now you can use this class in OITA - Investment Profile.
    And assign this Investment Profile to Project Profile in OPSA.
    Assign this Profile to capital project.
    Now all your assets which are AUC stage will come to this asset class.
    You can create completed asset in the other class by full settlement.
    Rewards for helpful answer.
    Thanks,
    RIYA

  • WBS with billing element but no Sales Order

    Trying to write a SQ01 query to find WBS with billing element but no sales order assigned.  Can anyone help?

    VBRP is the billing item table, OP is asking about the sales documents.
    Queries for something that does not exist might be tricky. Use the tables/fields mentioned above (not VBRP), but make sure to use LEFT JOIN to VBAP. In this case you'll get blank/initial values in the query when no sales record exist. If you do a regular INNER JOIN then you just won't see the WBS that don't have VBAK/VBAP records.

  • WBS with billing element but no sales order assigned

    Trying to write a SQ01 query to find WBS with billing element but no sales order assigned. Can anyone help?

    Such WBS elements can be identified using CN43N report also using proper filtering criteria.
    Fileting criterias:
    Billing element.
    Order accepted status.

  • Statistical WBS & WBS with Planning element in summarization

    Can statistical WBS and WBS with planning element are included in summarization?
    Thx

    Hi,
    Summarisation reports output  are same as the equivalent standard reports but they vary only in the hierarchical display of values. The hierarchy of the report depends on the fields you are using to create a summarisation hierarchy.
    Regards,
    Arul.

  • Upload data thru LSMW -WBS with 3 levels

    Hi PS Experts,
    My situation is like I have to upload data thru LSMW for all Levels!  As I m doing for only L3 WBS with PD it is going upto 14 steps and executing.But for Level 2 and Level 3 it is not executing. In the Step "Read Data" it is showing blank.
    Can v upload these multilevel data thru LSMW? or how is like?
    Thanks in advance,
    Sanju..

    Hi Virendra,
    I think that your solution is very good for my purpose.
    But in my implementation there is no way to insert a new element in an existing WBS, I can only edit attributes for an element already created, for example, in cj02.
    I checked all the menus but i didn't find any useful command.
    Could you send me a screenshot of the keypoint in which you can create the element different from the first level?
    Thank you very much.
    Giorgio

  • Re:WBS with Sales Order

    How assign WBS with sales order?

    Hi,
    WBS element will be assigned at the Sales order item level.
    Goto accounting document tab,here we can assign the WBS element.
    If you assign the WBS element then the cost centre and profit centre will be auto determined from it.
    CJ20n is the T.Code to check the WBS element.
    Regards,
    Krishna.

  • QRFC with ALE for outbound interfaces

    I'm working on a client that is using ERP 4.7 (R/3).  We would like to use the ALE qRFC addition to utilize the serialization concept.  In the partner profile, I see a check box that says "queue processing". To our understanding, it enables qRFC  with ALE. But how does the function module (FM) MASTER_IDOC_DISTRIBUTE determine which queue naming function module to call from transaction WE85?  WE85 is a transaction where you define a function module to set your queue name based on the control record or IDOC.  Do you pass the Rule Name from WE85 into the MASTER_IDOC_DISTRIBUTE and thus ALE calls the associated queue naming FM ? If so, what field do you set in the control record?

    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/05daa0b5133ca0e10000000a42189c/frameset.htm
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c7/4efe402762ef6fe10000000a1550b0/frameset.htm
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c2/4356429c69b430e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/e7/555e3c0f51a830e10000000a114084/frameset.htm
    Please go through this link.
    This would help you..

  • Distributing Variant BOM (bills of material) with ALE

    Hi all,
    we need to distribute variant BOMs from one client to another in the same system. But in SAP standard it's not possible to distribute variant BOMs with ALE.
    Has anyone an idea, how we could manage it?
    Best regards!
    Heike

    Have you tried message type : MATERIALBOM_CREATEBOMGROUP ,but i think you need to create custom program.
    Anurag

  • Settling WBS with Billing element indicator

    Hi Experts,
    I'm trying to settling a Project that contains WBS with 'billing element' indicator marked and others not.
    When I executed CJ88 to settle WBS to CO-PA, only settled wbs without 'billing element' indicator marked.
    Could you indicate me why WBS with 'billing element' indicator marked doesn't settle to CO-PA, is there something special for those WBS ?
    Thanks in advance,
    José Luis
    Edited by: José Luis  Rodríguez on May 4, 2011 2:15 AM

    Hi
    1 .First step is we need to run T: code: CJB2 to generate settlement rule,  if at all settlement profile is not assigned to your project profile and settlement rule is derived from settlement strategy define for the rule assigned in Project profile.,
    2. Once you run step one, it will assign the settlement rule to the WBS with billing element as well it will assign result analysis key into the WBS with billing element (if att alll RA key is not defined in Project profile).
    3. Now Run RA in tcode: KKA2 and save the results. exceute tcode CJIF to see the project results.
    4. Now run the settlement in CJ88, you will see that the costs are settled to PSG. this you can verify in costelemnt report also.
    thanks
    regards
    kishore

Maybe you are looking for