WholeSales Scenario in IS Retail

Hi,
I am working on the Whole Sale scenario in IS Retail in which my client is selling the goods from the Store 'A',but the stock is physically maintained in Distribution Center 'B' as the store A is very small. That means it is only the virtual stock in Store 'A'.Physical delivery is happening from 'B', but actually in the system it is happening in 'A'.
Actual requirement is when i do the sales order , my delivering store will be 'A'. If I do delivery , then the delivering plant should be 'B' and good should reduce from "A".
Can any one suggest me possible solution for this.
Rgds,
Amit

hi
An assortment defines which materials a store, a distribution center or a customer can be supplied with at any given time and can therefore be used to check purchase orders and sales orders.
Every retail site is assigned one (and only one) assortment. This assortment is created when the retail site is created, but is not assigned materials until the listing stage, where materials are assigned to assortments using the assortment modules to which these materials belong
WB70 Create assortment class
WB71 Change assortment class
WB72 Display assortment class
WB73 Delete assortment class
WB74 Maintain assortments to classes
WB75 Maintain classes to classes
WB76 Maintain assortments in class
WB77 Display assortments to classes
WB78 Display Class for Classes
WB79 Display assortments in class
WSOA2 Change assortments
WSOA3 Display assortments
WSOA4 Delete assortment

Similar Messages

  • IDoc to File Scenario Error ( IS - Retail )

    Hi all ,
    I was trying scenario IDoc (SAP ECC 6.0) (IS-Retail) to File scenario .
    When i trigerred IDoc from ECC system , it's showing sent successfully to external system or program.
    But the problem is it's not coming inside XI sxmb_moni .
    I have checked the ALE Configuration and SLD configuration .
    Everything is fine.
    When i run the TCODE WE05 for IDocs List in XI , it's getting stucked there and the Error showing is
    "IDoc: 0000000000000028 Status: IDoc with errors added
    External segment name E2WBB01003 cannot be interpreted "
    Even i tried with other IDoc WPDWGR it is showing the same error
    "IDoc: 0000000000000029 Status: IDoc with errors added
    External segment name E2WPW01 cannot be interpreted"

    Hi Ashwin,
    Please check :
    1.The SAP system from which you want to import the  IDocs contains function modules for calling metadata.
    2.You can import IDocs from SAP Release 4.0 and higher.Support Packages Required for IDoc Imports:
    Release    Minimum  Support Package Requirement
    40B                   SAPKH40B48
    45B                   SAPKH45B26
    46A                   SAPKB46A20
    46B                   SAPKB46B12
    46C                   SAPKB46C05
    3.check for the authorizations required to import.
    Also see SAP Notes 677732 (authorizations), 672745 (missing function modules), 212011 (access to IDoc metadata), and 718320.
    check http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
    *Pls: Reward points if helpful*
    Regards,
    Jyoti

  • Third Party Intercompany Export Scenario in IS Retail

    hi experts
    scenario is like this
    cutomer 1234(foreign customer e.g.USA customer) is order goods for company code 2001 company code 2001 transfer the requst to another company code 1001
    now company code 1001 issue goods to customer and raise bill to company code 2001and company code 2001 will raise bill to foreign customer 1234
    please guide how to map this scenario
    thanks in advance

    Hanumant Nimbalkar,
      1. a) How Can we inter-Link the respective transactions between Plant B001 to A001
               Plant B001( Company Code 2000 ) will raise P.O to Plant A001 ( Company Code 1000 )
    We use the Inter Company stock Transfer with Billing
    Partis involved:
    1. End Customer
    2. Supplying Plant
    3. Receiving plant
    2. from A001 to External Vendor
         Plant A001 ( Company Code 1000 ) will raise P.O to the External Vendor.
      We use Third Party process
    Process.
    1. First Company code 2000 - Plant B001 will raise a P.O to Company Code 1000 - Plant A001
    2. The Company code 1000 Receives the PO and Finds it has not stock within its plant
    3. The company code 1000 will raise a new PO with reference to PO sent by Company code 2000 to its vendor.
    4. The Company code 1000 asks the vendor to deposit the material in their plant site.(by providing plant A001 Address)
    5. The Vendor will raise an invoice to the Company code 1000
    6. Now From the company code 1000, from plant A001 STO will be performed keeping receiving plant as 2000
    7. An Intercompany invoice will be raised by plant 1000 to plant 2000
    8. The Plant 2000 after the receipt of the material / invoice will pay to Company code 1000
    9. The Company code 1000 in return will settle the vendor invoice.
    Regards
    Sathya

  • How can I generate IDOC(WPUUMS) from XML file in POSDM or in SAP Retail

    Hallo Retail expert,
                                I have following scenario,
    I have Retail Store who send me their daily sales report through Wincor Nixdorf Point of sale. There i am using standard POSLOG2 to SEEBURGER(its a middleware which act as Converter) xml format and then i post that data first in POSDM and then with BAPI i transfer or book that data to SAP Retail.
    Above is the one scenario which is working.
    This is the Second scenario.......
    I have some external Retail store, they dont have Wincor Nixdorf POS, so they send me their Sales Report through SEEBURGER(its a middle Hardware which act as Converter) and SEEBURGER Convert that Sales data to XML format. My question is....
    How can i upload or Convert a XML File into IDOC (WPUUMS)in SAP or in POSDM?
    any new suggestion are welcome.
    Thank you all in advance.
    regards,
    Niel

    Hi,
    1. To get the required XML Schema, use transaction code WE60 to go to the IDoc documentation -> enter the IDoc type you want to use (WPUUMS01). Flag control and data record. Then display the XSD by choosing Documentation -> XML Schema from the menue bar. Now you can donwload the XSD for usage in Seeburger.
    2. Create your mapping from the POS format into the IDoc XML format in Seeburger.
    3. Create an XML File Port in ERP or POS DM using transaction code WE21.
    3. To inbound the XML file from Seeburger into POS DM or SAP Retail Seeburger should trigger the function module EDI_DATA_INCOMING. Parameters for this FM are the Pathname to the XML file and the Portname you just created. Based on the port name the FM can derive the port type xml and the data will be handled as XML data.
    Regards Carsten

  • "Manual Planning in SAP Retail w/o MAP

    Hi
    Can we create "Planning Scenario in SAP Retail w/o MAP " ?
    Can we do manual plannings in SAP Retail w/o BI , MAP? if so whats the limitation?
    Which are possible  for the following scenrios in SAP Retail w/o MAP /BI
    1. Planning Scenario ( Budget Plan )
    2. OAPC
    3.OTB Plan
    Simply, Whats the limitations of SAP Retail in Planning?
    Can anyone explain me clearly and if any documents for the above will be greatful
    Regards
    Anis

    Hi Anis,
    Sorry it is not possible to do manual plannings in SAP Retail w/o BI , MAP.
    It need integration with BI.
    Regards
    jiten

  • Free Issue - condition in purchasing pricing & GRN - IS-Retail

    I am having following scenario in IS-Retail.
    Whenever my client is purchasing articles, he is getting some free issue materials also from vendor  alongwith actual po qty.
    Say, if he is ordering 100 Boxes of Tiles, he is getting 10 boxes free from vendor. So total qty is 110 Boxes against PO qty 100 Boxes.
    Stock needs to be updated thru' GRN as 110 Boxes whereas value need to be considered for 100 Boxes in same PO.
    Client is not ready to go for "FREE ISSUE" PO  for this qty 10 Boxes ( Free issue from vendor ) and he wants to track it in the same/actual PO.
    How to handle this in IS-Retail in calculation Schema/Pricing Procedure?

    Hi,
    Go to SPRO > Materials Management > Purchasing > Discount in Kind (Discount in Form of Bonus Goods) > Perform following steps;
    Maintain Discount-in-Kind Dependencies (Cond. Table)
    > Field Catalog
    > Create Free Goods Tables
    > Display Free Goods Tables
    Define Access Sequence And Discount-in-Kind Types
    > Maintain Access Sequence
    > Define Free Goods Types
    Define And Assign Discount-in-Kind Schema
    > Maintain Free Goods Schema
    > Determine Free Goods Schema
    XK02 - Under "Purchasing" Data of Vendor, activate "Grant discount in kind" field.
    MM02 - Under "Purchasing" view of Material, specify indicator "2" for field "Qual.f.FreeGoodsDis."
    Now Go to Purchase Info Record (ME11/ME12), under "Conditions" Tab, click on "Free Goods" Button (Ctrl+F1), and click on "EXCLUSIVE" button and maintain condition record for material, if Qty is 100 then 10 is fre of same material.
    Now create PO for 100 qty, it will add a new line item of additional 10 qty auto with free indicator.

  • SAP IS-Retail and Production process

    hi experts,
    i am working on SAP IS-Retail. We have a scenario like our retail client is basically deals with FMCG, Footwear, White goods, Fashion related Items. In these items some of the items are inhouse produced. So in this scenario how can we proceed this Production Process and enter Production Planning in SAP IS-Retail. Whether SAP IS-Retail supports Production Planning and Quality Management. If supports till what extent this supports. If not what is the alternative solution..
    Solution needs some what urgent basis...............
    if anyone provide a White Paper then also will be appreciated.......
    any suggestions also higly appreciated............
    Regards
    Venkat

    Venkat
    Try the following links. These should help. This may not be a completer answer but it should be the official SAP answer that you should communicate to your client.
    Standard Functions Used in SAP Retail with Articles ( http://help.sap.com/saphelp_erp2005vp/helpdata/en/92/b22aae5a2711d3ae46080009d2232d/content.htm )
    Standard Functions Not Supported in SAP Retail  ( http://help.sap.com/saphelp_erp2005vp/helpdata/en/92/b22ab45a2711d3ae46080009d2232d/content.htm )
    Also remember the official SAP recommendation there ,is not to use Articles and Materials in the same application instance.
    Milan.

  • SAP Retail Store

    Can you please confirm for me the following:
    In the Master Guide SAP for Retail Business Suite 2009 Document Version 1.2 u2013 October 2009, there are two scenarios for SAP Retail Store:
    Scenario1: In-Store Merchandise and Inventory Management (ITS) .................................................. 32
    Scenario2: In-Store Merchandise and Inventory Management (Web Dynpro)..................................... 36
    1) Is it true that the technical system landscape as depicted on page 32 requires an ITS 640 (i.e. the older version of NetWeaver04) to front end the Retail Server based on ERP6.0 EhP3 (i.e. NW7.0)? Or is this an error (may be a carryover from NW04 documentation) and that the Integrated ITS 7.0 which is part of the NW7.0 Web AS of the Retail Server ERP6.0 EhP3 can be used instead?
    2) While the two different scenarios are using two different technologies (i.e. ITS vs WebDynpro), they are also providing different functionallies as well, do you agree? If so, both can be used in parallel and scenario 2 doesn't replace scenario1. Is this a valid statement?
    e.g. Scenarion 1 (ITS) covers: procurement, goods movement, and sales postings, as well as processes for vendor, assortment, and price management. There are also processes for physical inventory, product
    lookup, promotions, and food services and catering.
    whereas Scenario 2 (WedDynpro) covers: sales, service, and operations business functions stores require to run effectively on a daily basis
    3) In Scenarion 2, it is mentioned that BI 7.0 and BI Content add-on 7.03 are mandatory component, is this true and if so why? Or can I use Scenario 2 without having to upgrade my BW3.5 to BI 7.0?
    Please respond as much as possible after each question while providing supporting notes or links to your answers.
    Thanks,
    Tobi

    Hi,
    Pl check the following link which will provide relevant details:
    http://help.sap.com/bp_bblibrary/500/html/R34_EN_UK.htm
    Regards,
    S.V.ManiKumaar

  • Cannot create collective PO for pull scenario

    Hello,
    We want to realize the basic distribution scenario (R43 in Retail Best Practice) which involves creating initial STOs from DC to stores and further creating collective PO. It looks like all basic setup has been done. Nevertheless the WF10 returns "No documents selected" error. Can anybody help please ?
    Best regards,
    Oleg

    Hi Oleg,
    Check the following :
    1. Supply source of the store must be "2" ( Internal).
    2. Supplying site must be assigned at the site master level, either at the site level or site/merchandise category level.
    3. Distribution profile in the respective DC ( based on point 2) must be Flowthrough ( Check config for the profile).
    Regards
    Prabhu

  • Dimension Table Larger Than Fact Table

    Hi,
    I need a solution to deal with a situation in my project. The master data for the Business Partner is close to 20 Mil and growing. The overall records in the fact table is only 1.5 to 2 Mil.
    I am looking for suggestions that can help me in designing a optimal data model which does not hinder the reporting performance. Reporting with 20 Mil records in Dimension and 10 times less data in the fact table is not common occurance. I guess this is a scenario that the retail Industries would have experinced due to the huge customer base.
    P.S: Segregation of the dimension is something that will not help. And its currently a line item dimension. So any thoughts apart from these will be highly appreciative.
    Thanks!
    Sajan R

    Hi Sajan Rajagopal ,
    I think u need to just go through the dimensions u had created so trat u can delete unnecessary infoobjects assigned to tat dimension and can build a dimension whcih has only those of master data.
    For Ex...for the material master when we checked we had huge amount of data more than ur's so we had made diffenet dimenons for material and batch and then we had tried to load the data for tat dimensions and it was working fine and also data loads also getting loaded fine..
    Please check ur dimensions once so tat required ones are defined correctly in the dimensions

  • Since regrade no increase in Upload Speed? Is this...

    Hi all,
    My BT Infinity has now been upgraded to the 80/20 service for just over a week. The download speed has doubled from 35 Meg to circa 70 Meg. But the upload speed is stuck at circa 7 Meg, which is good but it hasn't increased from the 40/10 service. I would expect the upload to be circa 14 Meg. Is there a reason why? Is there anyway to increase the upload speed even at the expense of download speed?
    Thanks
    Download speedachieved during the test was - 72.43 Mbps
     For your connection, the acceptable range of speedsis 12 Mbps-77.43 Mbps .
     Additional Information:
     IP Profile for your line is - 77.43 Mbps
    Upload speed achieved during the test was - 7.68Mbps
     Additional Information:
     Upstream Rate IP profile on your line is - 20 Mbps

    Try the upload speed test at http://mcslhr.visualware.com/myspeed/myspeed_line_capspeed.html.  The bt tester grossly underestimates upload speed, especially if you have significant latency.  It was giving mine as around 6 or 8, when a proper tester (as above) or a good real site was giving 17.  
    If you have problems with the capspeed tester above (it sometimes has Java issues), http://speedtest.net/ still suffers a little from underestimating upload, but not nearly as badly as the BT tester.  It gave 12 or 13 at the same time I was getting the above results.
    Now my line and latency are improved the differences are there but smaller: capspeed 17.0, speedtest 15.7, BT wholesale 13.7, BT retail 9.17.

  • Cross docking and flow throughs

    Hi Gurus,
    Can anyboday send me configuration steps in cross docking and flow through scenarios in is retail.
    thanks in advance.
    Regards,
    PS

    Hi,
    Explore following URL
    Collective Purchase Order
    Bye,
    Muralidhara

  • Idoc error 56 in inbound

    Hi Experts,
    I did one idoc transfer from Server A (ecc 5)to server B(ecc 6) .when i took the transaction   we02 in server A its showing green light and outbound idoc was gone to server B .when i took we02 transaction in server B its showing error 56 with red light ,but idoc that i send from server A reached here with diff idoc number in the inbound side ,I had taken this idoc and put it in we19 transaction and i found that in the inboud side recever port in not populating .i tried to put port name manually by using the inbound function module at that time it  works correctly ending  with green light and same material is created in server B.
    what should i do to make the inboud port to populate automatically .In partner profile of server B ,ports and maintained correctly . Is it because of  any server difference?(ECC 5 --> ECC6) .Please help .
    Regards
    Sarath
    Edited by: Sarath Madhusoodhanan on Feb 6, 2008 7:24 AM

    Best Practices for mySAP Retail
    Version 1.47
    based on
    SAP R/3 Enterprise with Retail Extension 1.10
    and SAP BW 3.0b
    Process Documentation Scenario
    EDI in Purchasing
    Copyright
    © Copyright 2003 SAP AG. All rights reserved.
    No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
    Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
    Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.
    IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.
    ORACLE® is a registered trademark of ORACLE Corporation.
    UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
    Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
    HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
    JAVA® is a registered trademark of Sun Microsystems, Inc.
    JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and Commerce One.
    MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
    SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.
    Table of Contents
    1     SCENARIO EDI IN PURCHASING     4
    1.1     Introduction     4
    1.2     Procedure     4
    1.3     Preconditions     7
    1.4     Scenario Menu and Basic Path     7
    1.5     Overview of Required Master Data     8
    2     EXECUTION     9
    2.1     Purchase Order Processing in the Retail System     9
    2.1.1     Create Purchase Order     9
    2.2     Sales Order Processing in the Vendor System     10
    2.2.1     Looking at IDoc ORDERS and ORDRSP     10
    2.2.2     Display Sales Order     10
    2.3     Control Order Confirmation in the Retail System     10
    2.4     Process Delivery in the Vendor System     11
    2.4.1     Posting Stock     11
    2.4.2     Create Delivery     11
    2.4.3     Picking and Goods Issue     12
    2.4.4     Looking at IDoc DESADV     12
    2.5     Post Goods Receipt with Reference to Shipping Notification in the Retail System     12
    2.6     Create Billing Documents in the Vendor System     13
    2.6.1     Creating Billing Documents     13
    2.6.2     Looking at IDoc INVOIC     13
    2.7     Display Incoming Invoice in the Retail System     13
    1     Scenario EDI in Purchasing
    1.1     Introduction
    To increase the efficiency of communication between retailers and vendors, documents such as purchase orders, order confirmations, shipping notification documents and invoices are transferred electronically. In the SAP R/3 System, this communication is supported by the creation of IDocs. An IDoc is an electronic document with the standard SAP format. Communication between two SAP R/3 Systems takes place using a converter and standardized national (SEDAS) or international (UN/EDIFACT) standards to transfer messages across a network (Wide Area Network, Local Area Network).
    In the following scenario, we at retail headquarters (Retail system) will be communicating with our vendor (Vendor system). As only one SAP R/3 System is available, while we are going through the handbook the two systems will be simulated using two company codes.
    As the retailer, in purchasing organization E001 we place orders for our distribution center VZ01 in purchasing organization V001, distribution chain V2 for >Article 1 with our vendor >vendor. Company code PS01 will be used to designate our organization. The vendor’s organization will be represented by purchasing organization V00L, distribution chain V3, supplying site LZ01 and company code PS0L. At retail headquarters, processing on the purchasing side will involve purchase orders, order confirmations, goods receipts and invoice verification.  On the vendor side, sales-side processing will be shown using sales orders, delivery documents and billing documents. To ensure adherence to the chronological procedure of the business process, we will continually be jumping between the retailer and the vendor. So that both sides are able to communicate with one another and so that subsequent functions in the business applications can be triggered, the vendor >vendor on the side of the retailer must be connected with the customer >customer on the side of the vendor. For more detailed information see the Customizing Guide for this process.
    1.2     Procedure
    The process flow is as follows:
    1.     Process purchase order in the Retail system
    2.     Process sales order in the Vendor system
    3.     Control order confirmation in the Retail system
    4.     Process delivery in the Vendor system
    5.     Carry out goods receipt with reference to shipping notification in the Retail system
    6.     Create billing documents in the Vendor system
    7.     Carry out invoice verification in the Retail system
    The following overview shows the individual steps again and the IDocs to be sent:
    Retail system     IDoc           IDoc           Vendor system
    Create purchase order     ORDERS          
                   Sales order is created, order confirmation is created
              ORDRSP     Process sales order
    Order is entered into the purchase order               
              DESADV     Create delivery
    Shipping notification is created               
    Carry out goods receipt for the shipping notification               
              INVOIC     Create billing document
    Incoming invoice is created, invoice verification is carried out               
    1.3     Preconditions
    1.4     Scenario Menu and Basic Path
    The following path is the basis for all other paths in this process documentation. As an alternative to the SAP menu, you can use the process menu for navigational purposes. You can access this using the button in the SAP Easy Access menu.
    BASIC PATH     SAP menu  Logistics  Retailing
    PROCESS MENU     PCS_RT_LOC4_040
    1.5     Overview of Required Master Data
    To carry out the scenario, use the master data listed for your installation of the preconfigured system. You can find corresponding identifiers in the following table:
         FASHION     HARD GOODS     FOOD
    MASTER DATA IN THE RETAIL SYSTEM               
    RETAIL ARTICLE     PCS-02-ART111     PCS-02-ART431     PCS-02-ART333
    VENDOR     PCS-V112     PCS-V432     PCS-V332
    DISTRIBUTION CENTER     VZ01     VZ01     VZ01
    MASTER DATA IN THE VENDOR SYSTEM               
    VENDOR ARTICLE      EDI-02-ART111     EDI-02-ART431     EDI-02-ART333
    CUSTOMER     PCS-C300     PCS-C320     PCS-C310
    SUPPLYING SITE     LZ01     LZ01     LZ01
    PURCHASE ORDER QUANTITY     500     500     500
    BASE UNIT OF MEASURE     PC     PC     PC
    2     Execution
    2.1     Purchase Order Processing in the Retail System
    2.1.1     Create Purchase Order
    The retailer creates a purchase order for the vendor >vendor in their SAP R/3 System (the purchase order could also be the result of a complex procurement scenario). Following this, the SAP R/3 System automatically sends an IDoc in ORDERS format using the standard EDI outbound.
    PATH     Purchasing  Purchase order  Purchase Order  Create  Vendor Known     ME21N
    ENTER     Vendor
    Order type
    Document date     >VENDOR
    'Standard purchase order'
    TABSTRIP     Organizational data     In “Header area” (expand if necessary)
    ENTER     Purchasing Org.
    Purch. Group
    Company Code     'E001'
    'E01'
    'PS01’
    BUTTON          In “Item Overview” area (expand if necessary)
    ENTER     Site     ‘VZ01’
    BUTTON          
    ENTER     Article
    PO quantity
    OUn     >Retail ARTICLE
    >PURCHASE ORDER QUANTITY
    >BASE UNIT OF MEASURE
    BUTTON          
    Only when using a generic article:
    MESSAGE     Enter variant quantities     
    ENTER     Distribute the total quantity among the variants     
    BUTTON          
    MESSAGE     Can delivery date be met?     Possible
    BUTTON          Only with message
    MESSAGE     The effective price is..., the article price is...     Possible
    BUTTON          Only with message
    BUTTON          
    MESSAGE     Standard PO created with number ... .     Note purchase order no.
    BUTTON          
    When the purchase order is created, an IDoc ORDERS is created, using message control, which is sent to the vendor..
    2.2     Sales Order Processing in the Vendor System
    The IDocs sent in this process are always available twice, once in the sender’s EDI outbound and once in the recipient’s EDI inbound.   The IDoc ORDERS that is sent by the Retail system enters the vendor’s system, ensuring that a sales order (standard order) is automatically created. At the same time an order confirmation ORDRSP is created and sent back to the retailer. When the order confirmation arrives in the Retail system, the sales order number is entered into the purchase order.
    2.2.1     Looking at IDoc ORDERS and ORDRSP
    PATH     SAP menu  Tools  Business Communication  IDoc Basis  WE02 - Display IDoc      WE02
    ENTER     Date of creation     
    BUTTON          
    SELECTION     Outbound IDocs and inbound IDocs ORDERS AND ORDRSP are displayed.
    Double click on IDoc ORDERS in inbound
    Double click on IDoc number
    Expand the controlling tree “status records”
    Expand the controlling tree “application document posted”
    Note down the number of the message “standard order number... saved.”     
    BUTTON     2 x      
    2.2.2     Display Sales Order
    PATH      Sales  Sales order  Order  VA03 - Display     VA03
    ENTER     Order     Order number from 2.2.1
    BUTTON          
    TABSTRIP           
         Site
    Confirmed quantity     ‘LZ01’
    >Purchase order quantity
    BUTTON     2 x      
    2.3     Control Order Confirmation in the Retail System
    PATH      Purchasing  Purchase order  Purchase Order  ME23N - Display      ME23N
    PATH     Purchase order  Other purch. order     
    ENTER     Purchase order
    Purchase order (radio button)      from 2.1.1
    ‘x’
    BUTTON          
    PATH     In “Item Overview” area (expand if necessary)
    TABSTRIP Confirmations
    The number of the sales order is entered in the field, External document     
    BUTTON          
    2.4     Process Delivery in the Vendor System
    The vendor creates a delivery with reference to the sales order, picks and posts the goods issue. When the goods issue is posted, a shipping notification (IDoc in DESADV format) is automatically sent. 
    2.4.1     Posting Stock
    So that the delivery can take place, there has to sufficient stock available in the vendor’s distribution center (LZ01). To ensure this is the case, CATT ZRT_3_1_MB1C can be started:
    PATH     SAP menu  Tools  ABAP Workbench  Test  Test Workbench  Test Tools  SECATT - Extended CATT      SECATT
    ENTER     Test Configuration     /BPR3R/EDI_BESTAND
    BUTTON          
    ENTER     Error behavior
    Variant
    (otherwise leave the default values)     S No termination, Continue with Next Script Command
    According to the selected master data:
    1 (Fashion),
    2 (Food) or
    3 (Hard goods)
    BUTTON          
    BUTTON     2 x      
    2.4.2     Create Delivery
    There is sufficient stock available for the delivery to be created.
    PATH      Sales  Sales order  Order  Subsequent Functions  VL01N - Outbound Delivery      VL01N
    ENTER     Shipping point
    Selection date
    Order     ‘LS01’
    See
    See 2.2.1
    BUTTON     
    MESSAGE     Delivery ... saved
    Note down the number of the delivery     
    BUTTON          
    2.4.3     Picking and Goods Issue
    The pick quantity is entered and the goods issue posted. Only after this has been done, is the IDoc created.
    PATH      Sales  Store order  Delivery  VL02N - Change     VL02N
    ENTER     Outbound Delivery      from 2.4.2
    BUTTON          
    TABSTRIP           
    ENTER     Pick quantity     >Purchase order quantity
    BUTTON     
    MESSAGE     Outbound delivery ... saved     
    BUTTON          
    MESSAGE     Outbound delivery ... saved     
    BUTTON          
    2.4.4     Looking at IDoc DESADV
    PATH     SAP menu  Tools  Business Communication  IDoc Basis       WE05
    ENTER     Creation Date
    Logical message     
    BUTTON     
    Outbound IDoc and inbound IDoc DESADV is displayed
    Double click on IDoc DESADV in inbound
    Expand the controlling tree “Status records”
    Expand the controlling tree “Application document posted”
    Note down the number of the message “ 0001 delivery (ies) of number ... to number ... created”.
    2 x      
    2.5     Post Goods Receipt with Reference to Shipping Notification in the Retail System
    The retailer posts the goods receipt with reference to the shipping notification.
    PATH      Merchandise logistics  Goods receipt   MB0A – Goods Receipt for Other Reference     MB0A
    ENTER     Movement Type
    Site
    Storage Location
    Shipping Notif.     '101’
    ’VZ01’
    ’0001’
    See 2.4.4
    BUTTON          
    BUTTON          
    MESSAGE     Document ... posted     
    BUTTON          
    2.6     Create Billing Documents in the Vendor System
    2.6.1     Creating Billing Documents
    The vendor creates a billing document that the retailer receives using EDI (IDoc in INVOIC format).
    PATH      Sales  Billing  Billing Document  VF01 - Create     VF01
    ENTER     Document      from 2.4.2
    BUTTON     
    MESSAGE     Processing document ... .
    Document ... saved     
    BUTTON          
    2.6.2     Looking at IDoc INVOIC
    PATH     SAP menu  Tools  Business Communication  IDoc Basis       WE05
    ENTER     Creation Date
    Logical message     
    BUTTON     
    Outbound IDoc and inbound IDoc INVOIC is displayed
    Double click on IDoc INVOIC in inbound
    Expand the controlling tree “Status records”. Expand the controlling tree “Application document posted”
    Note down the number of the message “order number... saved.”
    2 x      
    2.7     Display Incoming Invoice in the Retail System
    PATH     Retailing  Purchasing  Logistics invoice verification  Further processing  MIR4 - Display     MIR4
    ENTER     Invoice doc. number     See 2.6.2
    BUTTON     
    Thanks
    Amit Shivhare
    PS: Reward point

  • Two logon par files in a single EP instance?

    Gurus,
    We are working on EP 6.0 SP15. This is an external facing portal for retailers with backend BW 3.5.
    There is another wholesaler web application running on Standalone ITS with BW 3.1 and SAP R3 4.6 as backend.
    Requirement is to merge the wholesaler application with existing retailer application on EP 6.0 SP15.
    We can have 2 login pages ( one for retailer and one for wholesaler ) on EP 6.0 SP15 and the authentication concept should differentiante the users as retailer or wholesaler and users should be directed to their roles/pages.
    What would be the best approach to take considering the fact that there should not be any impact to the existing retailer application?
    Thanks
    Edited by: Sreenivas Varadharajan on Aug 12, 2008 2:24 PM

    Hi ,
    check below blog
    You can check the following blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5124. [original link is broken]
    It helps you to understand different logon pages for portal
    Koti Reddy

  • NEW ITEM IN INBOUND DELIVERY

    Hi All,
    We have an issue in inbound delivery. We have created a purchase order with one line item. While giving confirmation the vendors says that he would also send some free items along with the actually ordered items.
    For Example I create a PO for "Item-A  10 Qty"
    Vendor confirms he would send "Item-A 10 Qty and Item-B 10 Qty (As free)".
    The requirement is such that instead of updating the PO we would like to add it in the inbound delivery.
    and while doing GR against Inbound Delivery the system should do GR for Item-A as well as Item-B(As free item).
    Finally PO should be "Item-A 10 Qty"
    Inbound Delivery Should be "Item-A 10 Qty and Item-B 10 Qty"
    Goods receipt should be "Item-A 10 Qty and Item-B 10 Qty(As Free)".
    Is this possible in standard. If not what is the standard way of handling this scenario.
    Kindly advise.
    Thanks & Regards,
    Shakthi.

    Exclusive bonus quantity and Inclusive bonus quantity are the two standard scenarios available in retail. The problem u have discussed can be mapped using this.
    Steve,

Maybe you are looking for