Ans: SAP IS Retail has many different versions active in market, 4.0, 4.7 and currently more common new implementations are being done in ECC 5.0 and ECC 6.0.
Ans: MAP stands for Merchandise and Assortments Planning
Ans: Yes
Ans: Promotions are maintained via a transaction called WAK1, the pricing conditions are created and transferred down to POS or other systems.
Ans: Physical goods issue is posted as negative goods receipt when merchandise is returned
Ans: Plan markdown items, quantities, and pricesAssign storesUse markdown rules and schedules to control which items are active at what prices during each phaseSlow-Seller Management tool automates markdown schedule based on inventory and timingPre-season or in-season planning and executionVisibility to costs and key figuresFlexible ‘what-if’ simulations to achieve desired goals and marginsMass maintenance – many items, multiple levels, concurrent users can work the same markdown planAnalytics – create tailored reports to track KPIs, sell-through, and make adjustments, as neededIntegration to regular retail price management
Ans: Yes
Ans: We can use the space management data in requirements planning and replenishment.
Ans: One of the biggest drawback of using change pointers in a retail environment is the volume of change pointers that may get created and the ability of the system to handle those changes. Performance of batch jobs is severly affected when we have many change pointers. Proper care
should be taken to create only those change pointers, which will be consumed by the system.
Ans: Using MM41 transaction
Ans: Data migration should be handled as early as possible. It is recommended that even during the prototyping stage, do not stub the test data, and use the actual migrated sample test data from existing systems. This way business user will be looking at the actual data during demo. The most prevalent risk to conducting an SAP test whether it is integration, functional, string, volume, smoke, or security test is obtaining valid SAP test data. Where will the test data come from? How will one produce new data for transactions that require unique data? How will the data be loaded into a new SAP client and instance? What happens when an interface or conversion needs to send data into core SAP R/3 from a legacy system and the interface or conversion is not executing properly or has yet to be developed? What happens when the transactional data has not been created? All these are very important aspects and should be handled at a much earlier stage.
Ans: A stock transfer order is a PO that triggers the transfer of stocks between sites/stores within the same company
Ans: Normal Pricing in SAP IS Retail are maintained using VK11 using different condition type. Change pointers can be configured in the SAP system that will be triggered when any price change or price addition happens and these change pointers are transferred down to the POS
systems using POSDM or other custom solutions. The changes can transferred to other channels like website and mobile devices using the same strategy.
Ans: Yes, we can generate return deliveries to the sending store in the STO
Ans: Markdown are phased down reduction in prices, which may due to seasonal pricing, vendor sponsored price changes, effort to reduce inventory etc. Basically, markdowns provide strategy to reduce the price of a particular article in a phased down manners, equal or varying % of
price being reduced at a regular intervals. SAP IS Retail provides tools to manage this. It provides tools to plan a markdown, activate and send the data down to the stores. It also provides various reports to see how the different markdowns are doing.
Ans: No, a single vendor can always be associated with the PO
Ans: Space management deals with optimizing the positioning of an article on a shelf. key figures are defined that determine how the space will be managed, which is usually done based on sales data, revenue data or the gross margin.
Ans: Change pointers is a concept in SAP which allows the system to manage the changes happening to Master data, pricing or in general anything data change. Different change pointers are created and they are used to transfer the changes down to other systems like BW, POS, eBusiness,
Manugistics etc.
Ans: The bonus buy functionality in IS-Retail can be used to solve this case. You can create a bonus buy via a retail promotion or via sales condition master data.
If you first create a material grouping with all the articles in the combination, and then you create the bonus buy condition using that material grouping.
Check the bonus buy customizing in IMG —> Sales and distribution –> Basic functions —> Bonus.
Ans: Listing is a process which controls what stores get what articles. Articles which are listed to a particular store or DC will not get be able to process them. The Master data related with those articles will not be available in the stores where that article is not listed.21. What is EAN/UPC?
EAN is a European Artcile number and UPC is Universal Product Code.Each article should have a unqiue number.
Ans: Each unit of measures will have it’s own UPC or EAN numbers
Ans: Listing conditions are stored in the table WLK1. The important things apart from listing that WLK1 contains are validity dates and module numbers.
Ans: MARA, WLK2, MBEW, MAW1, MARC.
Ans: Reference site provides certain logistics data when creating or changing article data.
Ans: Generic article example – T-shirt is a generic article and the different variants of this article are Yellow, Red, Blue T shirts.
Ans: Pricing profile controls whether the variant sales prices are the same or different to the sales price of the generic article.
Ans: At POS when he presents coupons, POS gets details of coupons from SAP in form of IDoc, based on this, customer can avail a discount of X% on Apparel and Footwear Merchandise Category (MC). This percentage offer is not applicable for other MCs.
Ans: Source list is a list which determines from where a particular article can be procured from. Source list contains the vendor info, validity dates etc. A vendor could also be a store.
Ans: The equivalent Transaction of MM43 of the Retail-System in the Industrial System is MMo3.
Ans: HPR in Retail consists of programs specifically on the SAP to POS/BOS interface to improve the runtime of Master data (e.g. Article master/assortment list) IDoc generation. These programs are more efficient than the standard SAP programs. However, the end results are not exactly identical and certain enhancements are also not available in HPR.
Ans: It can be done through a couple of workarounds. First, using a little bit of PP. You can setup a production order, which consumes the Sugar in bulk bags and produces Sugar in 1 Kg bags. You can do costing on this and settle it to the finished product to get accurate costs. This will handle both the stock movement and also cost calculation.
Alternatively, you can have an additional surcharge condition type (e.g. packaging costs) that applies a fixed amount or % of cost to the specific products whenever the sell price (VKPo) is calculated. This is simpler and a one-off exercise that requires almost no maintenance on a day-to-day basis.
Ans: SAP WM perfectly manages this scenario. This will take several steps:
Define a fixed bin putway strategy for the warehouse/storage type (customizing for WM).
Ans: These coupons are created in IS-Retail using MM4i. Then you can use it in the bonus buy functionality as any other article. To limit the use of coupons to the Apparel and Footwear Merchandise Category you will have to create a material grouping including just these categories. The bonus buy condition will use the material grouping to grant the coupons.
You may also interested in...