If you're looking for SAP IS-Retail Interview Questions & Answers for Experienced & Freshers, you are in right place. There are a lot of opportunities from many reputed companies in the world. According to research SAP IS Retail has a market share of about 2.2%.
So, You still have the opportunity to move ahead in your career in SAP IS Retail. Mindmajix offers advanced SAP IS-Retail Interview Questions 2019 that helps you in cracking your interview & acquire a dream career as SAP IS Retail Developer.
|Types of SAP IS-Retail Interview Questions|
Top 10 SAP IS-Retail Interview Questions
SAP IS Retail has many different versions active in the market, 4.0, 4.7, and currently, more common new implementations are being done in ECC 5.0 and ECC 6.0.
MAP stands for Merchandise and Assortments Planning
|Explore - SAP Human Capital Management|
Normal Pricing in SAP IS Retail is maintained using VK11 using different condition types. 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 be transferred to other channels like websites and mobile devices using the same strategy.
Promotions are maintained via a transaction called WAK1, the pricing conditions are created and transferred down to POS or other systems.
Markdowns have phased down the reduction in prices, which may due to seasonal pricing, vendor-sponsored price changes, effort to reduce inventory, etc. Basically, markdowns provide a strategy to reduce the price of a particular article in a phased-down manner, with equal or varying % of the price being reduced at 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.
Plan markdown items, quantities, and prices assign stores to use markdown rules and schedules to control which items are active at what prices during each phaseSlow-Seller Management tool automate 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 margins miss maintenance – many items, multiple levels, concurrent users can work the same markdown plan analytics – create tailored reports to track KPIs, sell-through, and make adjustments, as needed integration to regular retail price management.
Change pointers are a concept in SAP that 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.
One of the biggest drawbacks 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. The performance of batch jobs is severely 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.
Using MM41 transaction
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 users will be looking at the actual data during the 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.
A stock transfer order is a PO that triggers the transfer of stocks between sites/stores within the same company
Yes, we can generate return deliveries to the sending store in the STO
|Explore - RPA For SAP|
Physical goods issue is posted as negative goods receipt when merchandise is returned
No, a single vendor can always be associated with the PO
Space management deals with optimizing the positioning of an article on a shelf. key figures are defined that determine how space will be managed, which is usually done based on sales data, revenue data, or the gross margin.
We can use the space management data in requirements planning and replenishment.
A source list is a list that determines where a particular article can be procured from. The source list contains the vendor info, validity dates, etc. A vendor could also be a store.
Listing is a process that controls what stores get what articles. Articles that are listed to a particular store or DC will not get be able to process. The Master data related to those articles will not be available in the stores where that article is not listed.
EAN is a European Article Number and UPC is Universal Product Code. Each article should have a unique number.
Each unit of measures will have its own UPC or EAN numbers
|Related Article - Complete list of SAP modules|
Listing conditions are stored in the table WLK1. The important things apart from the listing that WLK1 contains are validity dates and module numbers.
MARA, WLK2, MBEW, MAW1, MARC.
The reference site provides certain logistics data when creating or changing article data.
Generic article example – T-shirt is a generic article and the different variants of this article are Yellow, Red, Blue T-shirts.
The pricing profile controls whether the variant sales prices are the same or different to the sales price of the generic article.
If we take a business scenario in which there are coupons published in newspaper and customer takes the cutting to store to buy articles.
At POS when he presents coupons, POS gets details of coupons from SAP in form of IDoc, based on this, customers can avail a discount of X% on the Apparel and Footwear Merchandise Category (MC). This percentage offer is not applicable to other MCs.
Now, where and how can we create these bonuses buy promotions in SAP (i.e. How are these coupons created and how are they linked to promotions)?
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.
Is it possible to solve the following scenario through SAP- Retail: If you buy two books, you will get the cheaper one free?
The bonus buys 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.
What is the equivalent Transaction of MM43 of the Retail-System in the Industrial System?
The equivalent Transaction of MM43 of the Retail-System in the Industrial System is MMo3.
What is the use of HPR (High-Performance Retail)?
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.
If you are purchasing a Sugar Bag of to kg and in the warehouse, you are packing it in pieces of Kg each. How can you account for the cost that has incurred in W/H (i.e. How can you account for the cost of Bulk Breaking in SAP-IS-Retail)?
It can be done through a couple of workarounds. First, using a little bit of PP. You can set up a production order, which consumes the Sugar in bulk bags and produces Sugar in 1 Kg bags. You can do the cost 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 the cost to the specific products whenever the selling price (VKPo) is calculated. This is simpler and a one-off exercise that requires almost no maintenance on a day-to-day basis.
How SAP runs replenishment for the locations in a warehouse, which are used for sales, and when the stock is lower in these locations, the stock from other locations is moved there?
SAP WM perfectly manages this scenario. This will take several steps:
Define a fixed bin put way strategy for the warehouse/storage type (customizing for WM).