Transporttaion Cross Docking between EWM and ECC across company codes

Seceanrio is as follows:
We have an EWM managed site in GB, and an IM managed site in IE.
We would like to use the transportation cross docking solution from within Service Parts Management to transfer goods from GB to IE, (ECC > EWM > ECC) across company codes.
Is this possible within the standard SAP solution?
Thanks in advance,
Craig Bramhald

Hi Hari
Inter Company Purchase scenario works when the same material exists in both the company codes... I dont know how SAP would manage this in the case of Assets, when the Same Asset No is not existent in the other Co Code...
However, Refer 1523976  PurchaseOrderERPRequest_In_V1:Asset account assignment fails
This applies to EhP4 / EhP5 - But I dont know if you are using the enterprise service PurchaseOrderERPRequest_In_V1 ....
If not, better create an OSS message to SAP and check with them mentioning the notes that you have mentioned in your message
BR,Ajay M

Similar Messages

  • Cross docking in EWM

    Hi all,
    We are trying to create a cross docking scenario in EWM. We are trying for the EWM triggered opportunistic cross docking. With all the suggested config settings and master data, the process is not happening. Can anybody share a config document regarding steps to be followed for Cross docking (in EWM).

    kishore yerra wrote:
    Because your scenario is working manually the above may not be a major issue.
    That's right. I've checked my settings, but this doen't seem to be the problem. As said, it works fine when creating WT's manually.
    kishore yerra wrote:
    the way we can try and diagnose this would be to deactivate your entries for storage type search sequence and try to retain only one entry that you used for cross docking.
    I've changed the storage type search sequence for putaway, so that the only available storage type is the Goods Issue zone. The system now creates a WT for putaway in 9020. However, it doesn't link the stock to the outbound delivery order, so it actually acts like a putaway. So, this is not the solution unfortunately.
    kishore yerra wrote:
    Along with this put a closs monitor on SLG1 to understand the determination used when warehouse tasks are created.
    SLG1 shows the following error message when creating the WT:
    Immediate Actions Only: Condition Is Not Evaluated (Message no. SPPF_DET_CRM002)
    it also displays one interesting warning message:
    Action Merging: One Unprocessed Action with Equality Check (Message no. SPPF062)
    I'm not sure what to do next; any suggestions?
    Regards,
    Oliver

  • Any SAP Note for RFC Error between BI and ECC 5.0

    Hi..
    the RFC Destination between BI and ECC 5.0 is giving errors.
    Plz let me know if there is any Support pack  or any solution to fix this error.
    thanks..

    Hi,
    pls find the RFC connection details
    1 Prerequisites
    1.1 User Roles
    Use
    With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
    Technical name Description File name for upload
    B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
    B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
    C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
    B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
    Procedure
    Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
    2 Local Settings
    This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
    2.1 SAP R/3
    2.1.1 Define Client Administration (SAP R/3)
    Use
    This activity allows you to change Customizing settings.
    Prerequisites
    You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
    Procedure
    Run the following activity:
    SAP R/3 Role Menu Define Client Administration (SAP R/3)
    Transaction Code SCC4
    SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    Then carry out the following steps:
    1. Choose Display  Change.
    2. Confirm the warning message Caution: The table is cross client.
    3. Select your SAP R/3 client and choose Details.
    4. In the Change View Clients: Details screen, activate the following settings:
    u2022 Automatic recording of changes
    u2022 Changes to Repository and cross-client Customizing allowed
    u2022 eCATT and CATT allowed.
    5. Save.
    6. Go back to the SAP Easy Access menu.
    2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
    Use
    The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
    1. Define the systems as logical systems.
    2. Assign the logical system for the SAP R/3 System to a client.
    This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
    Logical systems are defined cross-client.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
    Transaction Code SPRO
    SAP R/3
    IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
    2. Choose New entries.
    3. In the column Log System, enter a name for the logical system that you want to create.
    4. In the column Name, enter a description of the logical system.
    Log. System Name
    where XXX is the system name
    and NNN is the client.
    5. Save your entries.
    A transport request for Workbench appears.
    6. Select an existing request or create a new request, if necessary.
    A transport request for Customizing appears.
    7. Select an existing request or create a new request, if necessary.
    2.1.3 Assigning Logical System to Client
    Use
    The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Assign Logical System to Client
    Transaction Code SCC4
    SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    2. Choose Display ® Change.
    3. Confirm the warning message The table is cross client.
    4. Select your R/3 client and choose Details.
    5. Enter the name of the logical system of your SAP R/3 client.
    6. Save and confirm the warning message Be careful when changing the logical system.
    7. Choose Back twice.
    2.1.4 Creating an RFC User (SAP R/3)
    Use
    To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
    The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Creating an RFC User (SAP R/3)
    Transaction Code SU01
    SAP R/3 Menu Tools  Administration  User Maintenance  Users
    2. In the User field, enter RFCUSER.
    3. Choose Create.
    4. On the Maintain User screen, enter the following data on the Tab entry screens:
    Address
    Last Name
    Function
    Logon data
    User type System
    Password LOGIN
    Profile
    Profiles SAP_ALL
    SAP_NEW
    S_BI-WX_RFC
    Defaults
    Logon Language EN
    5. Save your entries.
    2.3 SAP BW
    2.3.1 Define Client Administration
    Use
    This activity defines changes and transports of the client-dependent and client-independent objects.
    Procedure
    1. To perform this activity, choose one of the following navigation options:
    SAP BW Role Menu Local Settings ® Define Client Administration
    Transaction Code SCC4
    SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    2. Switch to change mode.
    3. Select your client.
    4. Choose details.
    5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
    6. In field Client Role enter Customizing
    7. Check the settings for changes and transport of client-specific objects and client-independent object changes
    If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
    Result
    Client administration has been defined to support the installation using Best Practices.
    2.3.2 Defining a Logical System for SAP BW (SAP BW)
    Use
    In this step, you define the logical systems in your distributed system.
    Prerequisites
    Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
    Transaction Code SPRO
    IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
    1. A dialog box informs you that the table is cross-client. Choose Continue.
    2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
    3. On the New Entries: Overview of Added Entries screen enter the following data:
    Field name Description R/O/C User action and values Note
    Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
    Name Textual Description of the Logical System Enter a clear description for the logical BW system
    4. Choose Save.
    If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
    If you want to continue with the next activity, do not leave the transaction.
    Result
    You have created a Logical System Name for your SAP BW client.
    2.3.3 Assigning Logical System to Client (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW
    Role Menu Assigning Logical System to Client (SAP BW)
    Transaction Code SCC4
    SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    1. In the view Display View "Clients": Overview, choose Display.  Change
    2. Confirm the message.
    3. Select your BW client.
    4. Choose Details.
    5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
    6. Save the entries and go back.
    2.3.4 Opening Administrator Workbench
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW Modeling  Administrator Workbench: Modeling
    Transaction Code RSA1
    1. In the Replicate Metadata dialog box, choose Only Activate.
    2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
    2.3.5 Creating an RFC-User (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu Creating RFC User
    Transaction Code SU01
    SAP BW Menu Tools  Administration  User Maintenance  Users
    Then carry out the following steps:
    1. On the User Maintenance: Initial Screen screen:
    a. Enter the following data:
    Field Entry
    User RFCUSER
    b. Choose Create.
    2. On the Maintain User screen:
    a. Choose the Address tab.
    b. Enter the following data:
    Field Entry
    Last Name RFCUSER
    Function Default-User for RFC connection
    c. Choose the Logon data tab.
    d. Enter the following data:
    Field Entry
    Password LOGIN
    User type System
    e. Choose the Profiles tab.
    f. Enter the following data:
    Field Entry
    Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
    g. Choose Save.
    Do not change the password of this user as it is used in RFC connections.
    2.3.6 Define RFC-USER as default (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW Role Menu Define RFC-USER as default (SAP BW)
    Transaction Code RSA1
    SAP BW Menu Modeling  Administrator Workbench: Modeling
    1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
    2. In the Global Settings/Customizing dialog box choose Glob. Settings.
    3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
    a. Choose Display  Change.
    b. Enter RFCUSER in the BW User ALE field.
    c. Choose Save.
    Hope this helps in solving u r problem
    Regards
    Ramakrishna Kamurthy

  • Difference between classic and ECC pca

    Hi All,
    Could someone please tell me what is the difference between Classic and ECC PCA?
    Regards
    Suresh

    Hi
                Enhancement of new general ledger flexibility, that is you can enter user-defined fields  and update the corresponding totals (Profit Center / Segment / Region). Many standard reports can evaluate the information from the user-defined fields.
    Due to the new document splitting function  (Online Split) you can create financial statements, if required, at the company code level as well as for entities, such as the Profit centers / Segment.
    Using the u201CDocument splittingu201D function (online document split), you can create balance sheets for company codes as well as for further entities such as the profit center . The balance is then set to 0 for each document for the profit center.
    There are no longer any time-consuming reconciliation tasks between FI and CO  for the end of period, since in real-time in Controlling, the system transfers cross entity processes into the new general ledger.
    Transactions 3KEH and 3KEI  from the classic Profit Center Accounting for maintaining proposal profit centers for balance sheet and P&L accounts are no longer used to set the profit center.
    Display of receivables and payable's per profit center real time ( if document splitting is active).
    Detailed information for the setting the Profit Center accounting in the New General Ledger:
    Define the update of the characteristics u201CProfit Centeru201D and u201CPartner Profit Centeru201D in the ledger by selecting the scenario u201CProfit center updateu201D.
    Define the field u201CProfit centeru201D as a splitting characteristic in the document splitting.
    Set the u201CZero balanceu201D indicator again for the added field u201CProfit centeru201D and you therefore have to create balance sheets on the profit center.
    Activate the required entry field check to ensure that the profit center is set in all postings.
    EC-PCA Profit Center Accounting u2013 Profit center accounting forms an interface between the operative controlling (CO) applications and the Enterprise Controlling (EC) module It reflects the actual and plan postings from operative controlling and settlements components with which it is in targeted in real-time. It then summarizes this data according to profit centers, which reflect the internal structure of areas of responsibility within the company code
    Regards
    Edited by: Dublin on Oct 26, 2009 12:17 PM

  • SNP planned order availability date difference between APO and ECC

    Hi,
    I have observed that SNP Planned order availability date is not matching between APO and ECC. Details are as follows.
    I ran SNP Optimizer with bucket offset of 0.5. After publishing the optimizer created planned orders to ECC, only start date is matching.
    Example:
    I am using PDS as a source of supply.
    Fixed production activity in SNP PDS is 1 day.
    GR processing time: 3 day
    After running optimizer planned order is created with dates explained below.
    Start date/time: 09.05.2011 00:00:00
    End date/time: 12.05.2011 23:59:59
    Availability date: 16.05.2011 00:00:00
    Because of bucket offset defined as 0.5 optimizer planned order availability is start of next monday.
    After publishing this planned order to ECC dates on the planned order is as follows.
    Start date: 09.05.2011
    End date: 09.05.2011
    Availability date: 12.05.2011
    I have not maintained any scheduling margin key in ECC. Also if I dont define the GR processing time, planned dates between APO and ECC always match. Can anyone explain the impact of GR time on the availability date.
    Regards,
    Venkat

    Hi Venkadesh,
    What's "state stamp"? Do you mean different time zone?
    note : 645597  mentioned by Nandha is very helpful:
    In standard, CCR will use duedate - "the available date of the output product".
    Nandha's words "In SAP APO, if the receipt date of the primary product deviates from the
    end date of the last activity of the order, the receipt date
    always identifies this as inconsistent. You cannot rectify
    inconsistencies of this type by using CCR."
    I guess in your PDS or PPM, the output product is not assigned to the End of the last activity. Someone changed it?
    Please CIF the PDS or PPM again.
    If you really want to apply a note, please use note 815509 as you're using planned order,
    and system will use order end  date in CCR instead.
    GR time is always considered. BR/Tiemin

  • Link between SRM and ECC invoice

    Dear gurus,
    I need to find the link between SRM and ECC invoice number, can you please provide me the related tables?
    Thank you in advance for your collaboration.
    Regards,
    Fuffo

    i don't have access to the system now but i guess will be table BBP_PDBEI.
    or you can go tcode BBP_PD, check in item level.
    cheers.

  • Synching the data between MDM and ECC

    Hi All,
    We have been on SAP MDM Central Master Data Management scenario for more then a year now. In the pas we have seen many issues ike - Syndication server failures, idoc failures due to which the data is not 100% in synch between MDM and ECC.
    Though we are working on the idoc failure tracking process but my question is this -
    I need to create an automated program which runs on a weekly basis finds the data which is out of synch in MDM and FEP and gives me the same. So the logic should be something like this - Pick up the records updated during the last week in MDM, look for those records in ECC. Compare field by field and give me the delta.
    Since it is a central master data management scenario hence there are cases in which records are created in MDM but not present in ECC may be because of syndication failures or idoc failures.
    Any one worked n a similar sort of program/logic? Kindly let me know your experiences as well in efforts to keep the data in synch.
    Regards,
    Indraveer

    Hello Indraveer
    Yes you can do it.
    You can configure exchange between ECC and MDM by schedule directly or through PI
    or
    SAP MDM 7.1 has own API for ABAP, JAVA, .NET. (5.5 for ABAP,JAVA, .COM)
    That may be abap transaction  or java(.net) application is working by schedule.
    more about MDM API you can read here:
      ABAP
    http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/edff445128209ce10000000a42189d/frameset.htm
    JAVA and .NET
    http://help.sap.com/saphelp_nwmdm71/helpdata/en/13/041975d8ce4d4287d5205816ea955a/frameset.htm
    JavaDocs
    http://help.sap.com/javadocs/MDM71/index.html
    Regards
    Kanstantsin Chernichenka

  • Vendor payment and customer recipts across company codes

    Hi all,
    We are having 4 company codes in US.The vendors and customers are spread across company codes.
    1st scenario:
    Vendor "abc" has a debit balance os 5000 in company code A. In company code B, the same vendor has credit balance of 10000.
    How can we net the balances in both compnay codes and pay the difference to the vendor. The client has separate house banks for each company code.
    2 nd scenario:
    A customer sends a check for 2500. which needs to be applied against company code A (500) and Company code B (2000)
    How does the payment and receipts needs to be applied across company codes. Kindly suggest.
    Regards,
    Amulya.
    Edited by: amulya chowdary on May 21, 2010 4:31 PM

    Hi,
    You need to configure cross company clearing thru OBYA.
    Your queries can be addressed either treating other company code as the vendor/customer or clearing to a inter company GL.
    Best Regards,
    Madhu

  • Switching between Design and JSP tabs add code?

    I am new to SJSC and I am taking the time to go through all of the little odds & ends of the IDE.
    I was looking at:
    http://blogs.sun.com/roller/page/tor?entry=computing_html_on_the_fly
    And I decided to try this.
    When I add the following in the JSP tab:
    <h:outputText binding="#{Page1.tableHtml}" id="outputText1"/>Save.
    Then click on the Design tab, then go back to the JSP tab, I now have:
    <h:outputText binding="#{Page1.tableHtml}" id="outputText1"/>
    <h:outputText binding="#{Page1.outputText1}" id="outputText1"/>It's late here, but this doesn't make any sense, why would switching between Design and JSP tabs add code?
    Thanks,
    --Todd                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    Girish: I followed these steps:
    1.) Downloaded:
    Sun Java Studio Creator 2, Multilanguage creator-2-windows-ml.exe 254.23 MB
    2.) When I started the install, I received the message:
    Welcome to Sun Java(TM) Studio Creator 2! You are installing: Sun Java Studio Creator 2 development environment Sun Java System Application Server Platform Edition 8.1 2005Q1 Update Release 2 Bundled database
    3.) Installed version:
    Product Version: Java Studio Creator 2 (Build 060120)
    IDE Versioning: IDE/1 spec=5.9.1.1 impl=060120
    Also, Under, the Palette window: Standard component list, there is a component labeled Output Text.
    When placed on a jsp, the following code is produced:
    <h:outputText binding="#{Page1.outputText1}" id="outputText1" style="position: absolute; left: 24px; top: 48px"/>Thanks,
    --Todd                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Control message "Purchase across Company codes is not allowed"

    Hello Gurus
    We are running SRM5.0 ECS using EP. If we attempt to create a SC that falls foul of the above validation, we get a message but only as a warning. Naturally if a warning, users will ignore and continue the purchasing process up to the point that the PO is created. However, when the PO is transferred to the ECC, we get the "Error in Process" status for the same message, but ECC validation routines have this set to an error and not a warning.  Evidently there is a discrepancy with severity between SRM and ECC. We want to ensure that SRM matches up to ECC so it is an error in SRM and not a warning.
    Searching the web, I see that the message id is KI-113. Can't be sure this is correct as the portal we use does not display the msg id. I've checked the message control config in SRM, and see nothing for the message. Further investigation reveals that in order to control messages through the config, you can only maintain those that are listed in BBPV_PDMSG. After searching for id or text, I still cannot see how I can escalate ths message to an error.
    Any ideas?
    Thanks
    Ian

    Hi peggy
    This message comes from your r/3 backend system. go to se91 KI - message no. 113 in sap r/3.
    it is not srm message.
    Error : Purchasing across company codes is not allowed
    BR
    Muthu
    Edited by: Muthuraman Govindasamy on Oct 13, 2008 10:17 AM

  • MM STO between Plants under the same company code

    Hi experts,
    Please guide on the configuration steps for doing STO between Plants unders the same company code.
    We have company code 100 in that Plants A B & C are theie. Each Plant can do STO to other Plant.
    How to configure this scenario?

    Dear,
    Please follow bellow path
    1. Create a vendor for the Company code of the receiving plant using account group 0007 via T-Code XK01.
    2. In the purchasing data view assign the supplying plant and the schema group
    3. Create customer with the sales area of the vendor.
    4. The shipping conditions, the delivering plant and the transportation zone determine the route in the STO.
    5. In the pricing procedure determination relevant to the STO assign document pricing procedure and customer pricing procedure to get the pricing in the invoice.
    6. Maintain condition records for pricing condition.
    7. Maintain carrier as a partner in the customer master.
    8. In OMGN select the supplying plant and assign the company code and sales area. Similarly select the receiving plant and assign the company code and sales area (The company code to which the plant is assigned to).
    9. Assign the delivery type and checking rule to the document type.
    10. And finally, assign the purchasing document type to the supplying plant and the receiving plant.
    11. Create the STO using T-Code ME 21N and save.
    12. Check for release strategy if any and release using T-Code ME 28.
    13. Create delivery in background using VL10G.
    14. If delivery is created, it is an indication of correct configuration and master data creation.
    Stock transfer between two plants in different company codes is known as inter company stock transfer.
    Material should be maintained in both supplying and receiving plant MM01
    Stock should maintain only in supplying plant MB1C
    Create receiving plant as a customer in supplying plants company code and sales area XD01
    Assign this customer number in receiving plant details OMGN
    Assign supplying sales area in supplying plant details OMGN
    Assign delivery type NB for in combination of supplying/ receiving plants.
    Create STO ME21N
    As it is normal there in the item details we should get shipping date i.e. customer number
    Go for Delivery VL10B
    Shipping point *****
    Select PO go for execute
    then select the delivery then go for delvy ............create delvy,,,, delvy number generated.
    Goods Issue VL02
    Delvy doc **********
    Click on picking
    enter the picking qty
    Click on PGI
    in the mean time check in the PO history you will get the details
    Goods receipt MIGO
    Stock transfers that include deliveries and billing documents/invoices are only possible between plants belonging to different company codes.
    If you want to carry out a cross-company-code stock transport order with delivery but without a billing document, you must set the Relevant for Billing (data element FKREL) indicator in Customizing of the item type to "blank" (Not relevant for billing).
    The following applications are involved in this type of stock transfer:
    ? Purchasing (MM-PUR) in entering the order
    ? Shipping (LE-SHP) in making the delivery from the issuing plant
    ? Billing (SD-BIL) in creating the billing document for the delivery
    ? Inventory Management (MM-IM) at goods receipt in the receiving plant
    Invoice Verification (MM-IV) at invoice receipt in the receiving
    Transfer of goods from one location to another location, it may be between plants within the same company code or in different company code's plants.
    within the company code, but plants,
    receiving plant will raise the STO in Supplying/issuing plant-ME21n,
    Supplying plant will deliver the goods to receiving plants ,
    then we need to pick n post the Goods Issue-VL02n,
    now when we can observe that the STO qty will be added into receiving plant and reduced in Delivering plant,
    To do this, we need do prior customization in SPRO-IMG,-
    material should be created in both plants( receiving & Supplying)
    -maintain the stock only in supplying plant
    -create a dummy customer in supplying plant's sales area(if u have one sales area, create in tat comp code n sales area)
    -assign this customer number to receiving plant's details along with the sales area,
    -Assign the STO doc type(UB) to Supplying plant, along with checking rule
    -Assign the Del type (NL/NLCC) to Supplying n receiving plant.
    Stock Transport Order:
    http://help.sap.com/saphelp_47x200/helpdata/en/4d/2b911d43ad11d189410000e829fbbd/content.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/4d/2b917843ad11d189410000e829fbbd/content.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/4d/2b918543ad11d189410000e829fbbd/content.htm
    u can also use the SAP building block
    with delivery
    http://help.sap.com/bestpractices/BBLibrary/html/P36_IntStockTransDel_EN_IN.htm
    without delivery
    http://help.sap.com/bestpractices/BBLibrary/html/P38_IntStockTransWithoutDel_EN_IN.htm
    Regards,
    Mahesh Wagh

  • Help - Error in PR BAPI :  Purchasing across company codes is not allowed..

    I have written a program to create Purchase Requisition.I am using two BAPIs.In the file i specify the old PR No, New Plant,Purch Group and Purch Org.It is actually a program to create a new PR in a new plant which is a copy of an Old PR in older plant.
    Program is below:
    I am getting the error Purchasing across company codes is not allowed..
    Please Help
    *& Report  ZMMB_BDC_ME51N_WO
    REPORT  ZMMB_BDC_ME51N_WO.
    INITIALIZATION.
    D A T A   D E C L A R A T I O N                                     *
      TYPES: BEGIN OF TY_TABDATA,
              BANFN TYPE EBAN-BANFN, " Purchase Requistion No
              WERKS TYPE MEREQ3211GRID-WERKS, "Plant
              EKGRP TYPE MEREQ3211GRID-EKGRP, "Purchasing Group
              EKORG TYPE MEREQ3211GRID-EKORG, "Purchasing Organization
             END OF TY_TABDATA.
      TYPES: BEGIN OF TY_CHECK,
                BANFN TYPE EBAN-BANFN, " Purchase Requistion No
                BNFPO TYPE EBAN-BNFPO, " Purchase Requistion Item No
                EBAKZ TYPE EBAN-EBAKZ, " PR Closed
             END OF TY_CHECK.
    Declaration of the Internal Table & Work Area.
      DATA:
             IT_TABDATA         TYPE  STANDARD  TABLE  OF   TY_TABDATA, " Internal Table for file
             WA_TABDATA         TYPE                       TY_TABDATA.
      DATA: IT_ITEM TYPE STANDARD TABLE OF BAPIEBAN ,
            WA_ITEM LIKE LINE OF IT_ITEM,
            IT_ITEM1 TYPE STANDARD TABLE OF BAPIEBANC,
            WA_ITEM1 LIKE LINE OF IT_ITEM1,
            IT_ACCOUNT TYPE STANDARD TABLE OF BAPIEBKN,
            WA_ACCOUNT LIKE LINE OF IT_ACCOUNT,
            IT_PRITEMTEXT TYPE STANDARD TABLE OF BAPIEBANTX,
            WA_PRITEMTEXT LIKE LINE OF IT_PRITEMTEXT,
            IT_SERVICES TYPE STANDARD TABLE OF BAPIESLL ,
            WA_SERVICES LIKE LINE OF IT_SERVICES,
            IT_SERVICES1 TYPE STANDARD TABLE OF BAPIESLLC ,
            WA_SERVICES1 LIKE LINE OF IT_SERVICES1,
            IT_SERVICETEXT TYPE STANDARD TABLE OF BAPIESLLTX,
            WA_SERVICETEXT LIKE LINE OF IT_SERVICETEXT,
            IT_CHECK TYPE STANDARD TABLE OF TY_CHECK,
            WA_CHECK LIKE LINE OF IT_CHECK.
       Global data Declaration
      DATA:   GV_YEAR(4)         TYPE C,
              GV_MNTH(2)         TYPE C,
              GV_DATE(2)         TYPE C,
              GV_DATUM(8)       TYPE C,
              GV_ANS TYPE C,
              W_FILENAME      TYPE  STRING.
    Declaration of the Internal Table with Header Line comprising of the uploaded data.
      DATA:  BEGIN  OF  IT_FILE_UPLOAD  OCCURS  0.
      INCLUDE  STRUCTURE  ALSMEX_TABLINE.  "  Rows for Table with Excel Data
      DATA:  END  OF  IT_FILE_UPLOAD.
    Batch Input Data for a single Transaction.
    Message of Call Transaction.
      DATA:  BDCDATA  LIKE  BDCDATA     OCCURS  0  WITH  HEADER  LINE,
             MSGTAB   LIKE  BDCMSGCOLL  OCCURS  0  WITH  HEADER  LINE.
    S E L E C T I O N - S C R E E N                                     *
      SELECTION-SCREEN:  BEGIN  OF  BLOCK  B1  WITH  FRAME TITLE TEXT-001,
                             BEGIN  OF  BLOCK  B2  WITH  FRAME TITLE TEXT-004.
      PARAMETERS: P_FNAME  LIKE  RLGRAP-FILENAME  OBLIGATORY.
      SELECTION-SCREEN:      END  OF  BLOCK  B2,
                         END  OF  BLOCK  B1.
    E V E N T : AT    S E L E C T I O N - S C R E E N                   *
    AT  SELECTION-SCREEN  ON  VALUE-REQUEST  FOR  P_FNAME.
      CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
        EXPORTING
          STATIC    = 'X'
        CHANGING
          FILE_NAME = P_FNAME.
    E V E N T : S T A R T - O F - S E L E C T I O N                     *
    START-OF-SELECTION.
    Upload Excel file into Internal Table.
      PERFORM  UPLOAD_EXCEL_FILE.
      IF  NOT  IT_FILE_UPLOAD  IS  INITIAL.
      Confirm whether you want to proceed with the Upload.
        PERFORM  CONFIRM_UPLOAD.
        IF  GV_ANS  EQ  '1'.
      Organize the uploaded data into another Internal Table.
          PERFORM  ORGANIZE_UPLOADED_DATA.
          PERFORM BAPI_CALL.
        ENDIF.
      ELSE.
        LEAVE PROGRAM.
      ENDIF.
    *&      Form  UPLOAD_EXCEL_FILE
          text
    -->  p1        text
    <--  p2        text
    FORM UPLOAD_EXCEL_FILE .
      CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
        EXPORTING
          FILENAME                = P_FNAME
          I_BEGIN_COL             = 1
          I_BEGIN_ROW             = 4
          I_END_COL               = 4
          I_END_ROW               = 9999
        TABLES
          INTERN                  = IT_FILE_UPLOAD
        EXCEPTIONS
          INCONSISTENT_PARAMETERS = 1
          UPLOAD_OLE              = 2
          OTHERS                  = 3.
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " UPLOAD_EXCEL_FILE
    *&      Form  CONFIRM_UPLOAD
          text
    -->  p1        text
    <--  p2        text
    FORM CONFIRM_UPLOAD .
      CALL FUNCTION 'POPUP_TO_CONFIRM'
        EXPORTING
          TITLEBAR       = TEXT-002
          TEXT_QUESTION  = TEXT-003
        IMPORTING
          ANSWER         = GV_ANS
        EXCEPTIONS
          TEXT_NOT_FOUND = 1
          OTHERS         = 2.
    ENDFORM.                    " CONFIRM_UPLOAD
    *&      Form  ORGANIZE_UPLOADED_DATA
          text
    -->  p1        text
    <--  p2        text
    FORM ORGANIZE_UPLOADED_DATA .
      DATA : GV_TOTROW TYPE I, "No of records
              GV_ROW TYPE I,
              LC_CNT(3) TYPE N.
      GV_TOTROW = 1.
      SORT  IT_FILE_UPLOAD  BY  ROW
                              COL.
      LOOP AT IT_FILE_UPLOAD.
        GV_TOTROW = IT_FILE_UPLOAD-ROW.
      ENDLOOP.
      GV_ROW = 1.
      WHILE GV_ROW <= GV_TOTROW.
        LOOP  AT  IT_FILE_UPLOAD WHERE ROW = GV_ROW.
          CASE  IT_FILE_UPLOAD-COL.
            WHEN '0001'.
              WA_TABDATA-BANFN = IT_FILE_UPLOAD-VALUE.
            WHEN '0002'.
              WA_TABDATA-WERKS = IT_FILE_UPLOAD-VALUE.
            WHEN '0003'.
              WA_TABDATA-EKGRP = IT_FILE_UPLOAD-VALUE.
            WHEN '0004'.
              WA_TABDATA-EKORG = IT_FILE_UPLOAD-VALUE.
          ENDCASE.
        ENDLOOP.
        GV_ROW = GV_ROW + 1.
        APPEND WA_TABDATA TO   IT_TABDATA .
        CLEAR :WA_TABDATA.
      ENDWHILE.
    ENDFORM.                    " ORGANIZE_UPLOADED_DATA
    *&      Form  BAPI_CALL
          text
    -->  p1        text
    <--  p2        text
    FORM BAPI_CALL .
      DATA:ITM_NO(4) TYPE N,LV_PERCENTAGE(3) TYPE N,
           LV_MSG(60),
           IT_RETURN TYPE STANDARD TABLE OF BAPIRETURN,
           WA_RETURN LIKE LINE OF IT_RETURN.
      DATA: BEGIN OF WA_RETURN1,
            BANFN TYPE EBAN-BANFN.
      INCLUDE  TYPE BAPIRETURN.
      DATA END OF WA_RETURN1.
      DATA:IT_RETURN1 LIKE STANDARD TABLE OF WA_RETURN1.
      DESCRIBE TABLE IT_TABDATA LINES ITM_NO.
      LOOP AT IT_TABDATA INTO WA_TABDATA.
        CALL FUNCTION 'BAPI_REQUISITION_GETDETAIL'
          EXPORTING
            NUMBER                               = WA_TABDATA-BANFN
           ACCOUNT_ASSIGNMENT                   = 'X'
           ITEM_TEXTS                           = 'X'
           SERVICES                             = 'X'
           SERVICE_TEXTS                        = 'X'
          TABLES
            REQUISITION_ITEMS                    = IT_ITEM
           REQUISITION_ACCOUNT_ASSIGNMENT       = IT_ACCOUNT
           REQUISITION_TEXT                     = IT_PRITEMTEXT
      REQUISITION_LIMITS                   =
      REQUISITION_CONTRACT_LIMITS          =
       REQUISITION_SERVICES                 = IT_SERVICES
       REQUISITION_SERVICES_TEXTS           = IT_SERVICETEXT
      REQUISITION_SRV_ACCASS_VALUES        =
      RETURN                               =
        COMPUTE LV_PERCENTAGE = ( ITM_NO / SY-TABIX ) * 100.
        CONCATENATE 'PROCESSING PURCHASING REQUISITION FOR OLD PR NUMBER ' WA_TABDATA-BANFN INTO LV_MSG.
        CALL FUNCTION 'RM_SAPGUI_PROGRESS_INDICATOR'
          EXPORTING
            PERCENTAGE = LV_PERCENTAGE
            TEXT       = LV_MSG.
        CLEAR:LV_PERCENTAGE ,LV_MSG.
        IF IT_TABDATA[] IS NOT INITIAL.
          SELECT BANFN BNFPO EBAKZ FROM EBAN INTO TABLE IT_CHECK FOR ALL ENTRIES IN IT_TABDATA
              WHERE BANFN = IT_TABDATA-BANFN AND EBAKZ = 'X'.
        ENDIF.
        LOOP AT IT_CHECK INTO WA_CHECK.
          LOOP AT IT_ITEM INTO WA_ITEM WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
            DELETE IT_ITEM WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
          ENDLOOP.
          LOOP AT IT_ACCOUNT INTO WA_ACCOUNT WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
            DELETE IT_ACCOUNT WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
          ENDLOOP.
        ENDLOOP.
        LOOP AT IT_ITEM INTO WA_ITEM.
          WA_ITEM-PLANT = WA_TABDATA-WERKS.
          WA_ITEM-PUR_GROUP = WA_TABDATA-EKGRP.
          WA_ITEM-PURCH_ORG = WA_TABDATA-EKORG.
          MODIFY IT_ITEM FROM WA_ITEM TRANSPORTING PLANT PUR_GROUP PURCH_ORG.
          MOVE-CORRESPONDING WA_ITEM TO WA_ITEM1.
          WA_ITEM1-PREQ_NO = ''.
          WA_ITEM1-STORE_LOC = ''.
          APPEND WA_ITEM1 TO IT_ITEM1.
          CLEAR WA_ITEM1.
        ENDLOOP.
        LOOP AT IT_ACCOUNT INTO WA_ACCOUNT.
          WA_ACCOUNT-PREQ_NO = ''.
          MODIFY IT_ACCOUNT FROM WA_ACCOUNT TRANSPORTING PREQ_NO.
        ENDLOOP.
        LOOP AT IT_SERVICES INTO WA_SERVICES.
          MOVE-CORRESPONDING WA_SERVICES TO WA_SERVICES1.
          APPEND WA_SERVICES1 TO IT_SERVICES1.
          CLEAR WA_SERVICES1.
        ENDLOOP.
        CALL FUNCTION 'BAPI_REQUISITION_CREATE'
       EXPORTING
         SKIP_ITEMS_WITH_ERROR                =
         AUTOMATIC_SOURCE                     = 'X'
       IMPORTING
         NUMBER                               =
          TABLES
            REQUISITION_ITEMS                    = IT_ITEM1
           REQUISITION_ACCOUNT_ASSIGNMENT       = IT_ACCOUNT
           REQUISITION_ITEM_TEXT                = IT_PRITEMTEXT
         REQUISITION_LIMITS                   =
         REQUISITION_CONTRACT_LIMITS          =
          REQUISITION_SERVICES                 = IT_SERVICES1
         REQUISITION_SRV_ACCASS_VALUES        =
           RETURN                               = IT_RETURN
          REQUISITION_SERVICES_TEXT            = IT_SERVICETEXT
         REQUISITION_ADDRDELIVERY             =
         EXTENSIONIN                          =
        READ TABLE IT_RETURN INTO WA_RETURN INDEX 1.
        IF WA_RETURN-TYPE = 'E'.
          CLEAR WA_RETURN.
          LOOP AT IT_RETURN INTO WA_RETURN WHERE TYPE EQ 'E'.
            WA_RETURN1-BANFN = WA_TABDATA-BANFN.
            MOVE-CORRESPONDING WA_RETURN TO  WA_RETURN1.
            APPEND WA_RETURN1 TO IT_RETURN1.
            CLEAR WA_RETURN1.
          ENDLOOP.
        ELSE.
          WA_RETURN1-BANFN = WA_TABDATA-BANFN.
          MOVE-CORRESPONDING WA_RETURN TO  WA_RETURN1.
          APPEND WA_RETURN1 TO IT_RETURN1.
          CLEAR WA_RETURN1.
        ENDIF.
        IF SY-SUBRC <> 0.
        ENDIF.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
           EXPORTING
             WAIT          =
           IMPORTING
             RETURN        =
        REFRESH: IT_RETURN[],IT_ITEM[],IT_ACCOUNT[],IT_PRITEMTEXT[],IT_ITEM1[],IT_SERVICES[],IT_SERVICES1[],
                 IT_SERVICETEXT[].
      ENDLOOP.
      WRITE :10 'OLD PR NUMBER' COLOR COL_KEY, 25 'MESSAGE' COLOR COL_KEY.
      LOOP AT IT_RETURN1 INTO WA_RETURN1.
        WRITE:/10 WA_RETURN1-BANFN,25 WA_RETURN1-MESSAGE.
      ENDLOOP.
      CLEAR:IT_TABDATA[],WA_TABDATA.
    ENDFORM   .                 "BAPI_CALL

    Solved on Own

  • Double Invoice check across company code

    Hi All,
    I have been trying to use the double invoice check functionality across company codes. i.e. when an invoice is posted in Company code A with ref no: xxx, and when I try to post a new inovice with the same reference ie. xxx in company code B, system does not give error message.
    Please note: I have maintained message in application F5, no: 117 and 312.
    Also in customization for double invoice check, I have unchecked "Check Company code" and checked "check reference" and "check invoice date"
    I have also maintained the double invoice check flag in the vendor master.
    Please help at the earliest.
    Regards,
    Ankush

    Hi Ankush,
    Good Day,
    Duplicate invoice check across company code will not check for FI related invoice ( Like FB60)
    But you can able to achive this with BTE ( SAMPLE_PROCESS_00001110 for FI Duplicate invoice check)
    Steps for Implementing a BTE
    (1)Goto transction FIBF menu Environment->Info System (P/S )
    (2)Select the BTE you want to implement.
    (3)Press button Sample function module
    (4)This brings you to SE37 - Copy the sample function module to a Z-function module (First create a new function group for the function module) . Note: The name of the Z-functionmodule is not important
    (5)Edit the code in the new function module
    (6)Go back to transaction FIBF - Menu Settings->Products -> Of a customer and create a new product whicj identifies the new product . Remember to mark the Active field.
    (7)Go back to FIBF menu Settings->P/S function modules->of a customer - Create an entry that links the BTE and Product with the new function module
    Best Regards,
    KSK

  • Purchase across company codes

    Hello,
    We are using extended classic & SRM 5.0.
    We have only one Sourcing specialist for The Netherlands and Belgium companies ( Company Codes), so can we assign the same Sourcing specialist to 2 different Purchase Groups which are defined for separate company codes - BE & NL. I have checked via Responsibility tab for the Purchase Groups but it will be possible for same Company code but not for cross company codes to do the Sourcing.
    Any idea how it is possible.
    Regards,
    Lovkesh

    HI lovkesh
    i think it is not possible.
    however chek some badi repository.
    for eg. in one shopping card , you can not order for two company codes.
    for eg- 10000001 sc  item 1 -1000 company  code
                10000001 sc item 2 - 2000 company code.
    br
    muthu

  • Stock Transfer Between two plants within same company code

    Hello,
    We are using scenario-'Stock transfer between two plants within same company code. Scenaro is like Plant A is receving plant and Plant B is delivering Plant.
    Plant A release PO for 100 nos to Plant B
    Plant B issues 100 nos (via delivery) to Plant A
    But Plant A receives only 50 nos physically so they do Goods receipt for 50 nos , but document got generated for 100 nos (when plant B issues material).
    Now Plant A do not want to receive remaining 50 nos physically, but wants to reduce material document which got created when goods issue posted by plant B
    Now stock in transis (mb5t) is 50 nos.
    How to reduce this material document. or any another alternative solution for this?
    Thanks,
    Shailesh

    Hi There
    Reversal of partial is not possible ,
    But you can use the Mov Type 557 and 558 to do the adjustments in Stock in transit qty
    Few more details on STO adjustments
    Hi There
    it can be settle in many ways,,,
    1. Receive the goods as 100 and Scrap the 50 nos from the received plant,,- If the receiving plant is responsible
    2.Revert the PGI/Transfer movement(Vl09) and send the 50 nos again from the supplying plant- of the Supplying plant is responsible,
    3.Also we have the movement type 557 and 558 without doing the above two steps you can correct the qty from stock in transit itself,,
    4. also you can check the below similar thread
    STO - material lost during tranfer from plant A to plant B
    5. If above are not ok, then receive the goods as 100, And raise the STO as your plant as supplying plant and receiving plant is (Supplied 50 nos less) plant,, Do the process without sending the material.. in this way that 50 nos can be adjusted,,
    6.Here is some more details
    557 Issue from stock in transit (adjustment posting)
    Only use this movement type (also the reversal movement type) under the following circumstances:
    Using movement type 557, you can correct purchase-order-independent stock in transit if
    - a good receipt cannot be posted to a purchase order without stock in transit, even though there is still stock in transit according to the purchase order history
    - stock in transit still exists, even though there are no open stock transfer orders for the particular material
    This movement type may ONLY be used in the cases mentioned above after careful analysis, to correct stock in transit that has rounding errors.
    This movement type may not be copied.
    Note!
    Before using this movement type, note the following:
    - 392205 Analysis stock in transit / Correction if split valuation
    Possible special stock indicators:
    E, Q
    7. As previous post says if you have the note for this issue you can use that also
    You can use any one of the way to solve the issue, Hope it helps
    Cheers
    Senthil P

Maybe you are looking for