Revaluation in Retail

Dear all,
I'm setting up the logistics extraction in a retail environment. For Revaluations, standard BC infosources & data sources are available. Can somebody please tell me what the difference is between 2LIS_03_UM and 2LIS_40_REVAL? Should I use both or only one? And in case of the 2LIS_40_REVAL, is the load procedure equal to 2LIS_03_UM as explained in several load scenarios?
Thanks for your help, points will be awarded.
Regards,
Joost

Hi,
2lis_03_um is one of the Data Source under that Application which contains data valuated revaluations in Financial Accounting. This Data is required to update Valuated Stock changes for the calculated stock balance in the BW.
NOTE : Only Stock value is changed here, not the Quantities.
2lis_o3_bx is used to extract an Opening Stock Balance on a detailed level.
2lis_03_bf is used to extract the material movements into the BW
Pls Try this link:
https://websmp202.sap-ag.de/~sapdownload/011000358700000206482005E/HowToInventoryNW.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/41/3d773d75316411e10000000a114b54/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5b/8dc73cee4fb55be10000000a114084/content.htm
Hope this helps,
Regards
CSM Reddy

Similar Messages

IS-Retail BI 7.0

Hi Experts,
We have a requirement of BI-IS Retail. Pls share your knowledge in BI IS-Retail,
Pls forward any documnets with BI 7.0 .
Pls don't include any SAP help link, i am working on this...
mail ID: [email protected]
Regards,
Rams.

Hi,
BW SAP Retail
http://help.sap.com/saphelp_nw04/helpdata/en/86/39d6386e24f90ae10000000a114084/content.htm
Revaluation at Retail
http://help.sap.com/saphelp_nw04/helpdata/en/8e/65f438c842cc2be10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/73/d26594107711d4af1e080009d2232d/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/35/e58282fe8711d3b49f006094b9301e/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/39/e531c93747da4a8806612212b013b4/content.htm
www.service.sap.com/bi -->>solution detail -->>Industry Portfolios -->> Sap Retail
http://service.sap.com/bi
http://help.sap.com/content/documentation/industry/docu_is_retail.htm
http://help.sap.com/content/documentation/industry/docu_is_retail_retail.htm
http://help.sap.com/content/bestpractices/industry/bestp_industry_retail.htm
Regards
CSM Reddy

Need you inputs on IS Retail Implementation

Hi Folks,
I need to work on IS retail implementation project and new to retail industry.
Can anyone send me the documents on on IS Retail and sap help link of that module so that i can understand what are standard cubes,reports are been usen in that.
I am also looking for the configuration document required for the data flow from POS TO BI through POS-DM.
And before starting into this project any other modules to be known. Please gudie me on this.
And if possible add some extra thing i am missing anything.
Points Assured.
Urs,
RK.

Hi,
Pls chk this link:
http://help.sap.com/saphelp_nw04/helpdata/en/86/39d6386e24f90ae10000000a114084/frameset.htm
http://help.sap.com/content/documentation/industry/docu_is_retail.htm
http://help.sap.com/content/documentation/industry/docu_is_retail_retail.htm
http://help.sap.com/content/bestpractices/industry/bestp_industry_retail.htm
Revaluation at Retail
http://help.sap.com/saphelp_nw04/helpdata/en/8e/65f438c842cc2be10000000a114084/content.htm
BW SAP Retail
http://help.sap.com/saphelp_nw04/helpdata/en/86/39d6386e24f90ae10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/73/d26594107711d4af1e080009d2232d/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/35/e58282fe8711d3b49f006094b9301e/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/39/e531c93747da4a8806612212b013b4/content.htm
You will get some more info from www.service.sap.com/bi -->>solution detail -->>Industry Portfolios -->> Sap Retail
http://service.sap.com/bi
https://websmp105.sap-ag.de/~sapidb/011000358700002346292001
https://websmp105.sap-ag.de/~sapidb/011000358700001897452001
Hope this helps,
regards
CSM Reddy

BW Retail content

Hello gurus
Could anyone please send me any documents regarding the BW retail implentation.. i hve the PDF but i need some more if any available.
Also could anyone send me the link for 2LIS_40_REVAL from saphelp.
regards
Ram

Hi Ram,
Have a look:
Revaluation at Retail
http://help.sap.com/saphelp_nw04/helpdata/en/8e/65f438c842cc2be10000000a114084/content.htm
BW SAP Retail
http://help.sap.com/saphelp_nw04/helpdata/en/86/39d6386e24f90ae10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/73/d26594107711d4af1e080009d2232d/content.htm
You will get some more info from www.service.sap.com/bi -->>solution detail -->>Industry Portfolios -->> Sap Retail
https://websmp104.sap-ag.de/bi
Hope it Helps
Srini

Is Retail Tcodes and Tables

HEllo
I would like to know from where we can get the list of Tcodes and Tables related to IS Retail
Regards
Mohammed

Hi ,
Pl find below list of Retail TCodes :
R11 Merchandise Related Master Data
Transaction code transaction text
SU3 Maintain User Profile
MM41 Create Article
MM42 Chang Article
MM43 Display Article
WSL11 Evaluation of listing condition
WSO7 Display Assortment Module Assignment to Assortment
MASS_MARC Logistic/replenishment Mass Maintenance
REFSITE Reference Sites Mangement
WSL1 Listing conditions
MR21 Price Change
MB1C Enter Other Goods Receipts
MB1B Enter Transfer Posting
MB03 Display Transfer Posting
RWBE Stock Overview Generic Articles
R12 Retail Pricing
Transaction code transaction text
SU3 Maintain User Profile
VKP5 Create Price Calculation
WPMA Direct Request For POS Outbound
WMB1 Create Price Entry
WKK1 Create Market-basket Price Calculation
SPRO Assign Price Point Group to Org. Level/Merchandise Category
WVA3 Display VKP Calcultion Sur
WVA7 Display VKP Calcultion Sur
WEV3 Display Ret. Markup SP Ca
MEKE Conditions By Vendor
ME21N Create Purchase Order
V-61 Create Customer Discount Condition
V-64 Display Customer Discount
VK13 Display Condition Records
V/LD Execute Pricing Report
VA01 Create Sales Order
MEI4 Create Automatic Document worklist
BD22 Delete Change Pointers
WVN0 Generate Pricing Worklist
WVN1 Release Worklist
R13 Assortment Management
Transaction code transaction text
SU3 Maintain User Profile
WSOA3 Assortment Display
WSOA1 Assortment Create
WSOA2 Assortment Change
WSOA6 Assortment Assignment Tool
REFSITE Reference Sites Mangement
WSL5 Modules In Assortment
MM41 Create Article
MM42 Chang Article
WSL1 Listing conditions
WSP4 Create Individual Listing Material / Assortment
WSO1 Assortment Module Create
WSO5 Maintain Assortment Module assignment to Assortment
SE38 ABAP Editor
WLWB Space Management: Layout Workbench
WPLG Display Article In Layout Module
WLCN Delete All Listing Conditions From Layout Module
WSOA1 Assortment Create
WSK1 Assortment Copy
WSPL Display / edit article master segments that cannot be generted
WSL0 Merchandise Categories Article Assortments Consistency Check
WSP6 Delete Individual Listing Material/Assortment
WSM8 Reorganize Listing Conditions By Merchandise Category
WSM4A Automatic Relisting Via Change to Assortment Master Data
WSL11 Evaluation of listing condition
WB02 Site Change
MB1C Enter Other Goods Receipts
WSE4 Article Discontinuation( Article / Site Discontinuation)
WSM9 Deletion of Obselete Listing Conditions
SE16 Data Browser
R21 Procurement of Replenishable Merchandise
Transaction code transaction text
SU3 Maintain User Profile
MM42 Chang Article
MP30 Execute Forecast: Initial
MP33 Forecast Reprocessing
MD21 Display Planning File Entries
MD03 Requirements Planning Single-Item, Single-Level
MD05 RP List
MD04 Stock/Requirements List
MB01 Enter Other Goods Receipts
ME01 Maintain Source List
ME51 Create Purchase Requisition
ME52 Change Purchase Requisition
ME59 Automatic Creation of Purchase Orders from Requisitions
ME21N Create Purchase Order
MIGO Goods Receipt for Purchase Order
ME13 Display Info Record
ME31K Create Contract
ME33K Display Contract
RWBE Stock Overview
MB1C Enter Other Goods Receipts
WWP1 Planning Workbench
WWP3 Planning Workbench
SPRO Maintain Rounding Profile
WB02 Site Change
MK02 Change Vendor
MD04 Display Stock/Requirements Situation
WLB1 Determining Requirements for Investment Buying
WLB6 ROI-Based PO Proposal for Purchase Price Changes
WLB2 Investment Buying Analysis
WLB13 Automatic Load Building
WLB4 Results List for Automatic Load Building Run
WLB5 Combine a Number of POs to Create a Collective Purchase Order
ME2L Purchasing Documents per Vendor
ME23N Display Purchase Order
ME61 Maintain Vendor Evaluation
ME63 Calculate Scores for Semi-Automatic and Automatic Subcriteria
ME64 Evaluation Comparison
ME65 Ranking List of Vendors
ME6B Ranking List of Vendor Evaluations Based on Material/Material Group
R22 Procurement of Non-replenishable Merchandise
Transaction code transaction text
SU3 Maintain User Profile
MM41 Create Article
MM42 Chang Article
WSL1 Listing conditions
MR21 Price Change Overview
ME51 Create Purchase Requisition
ME41 Create RFQ
ME47 Maintain Quotation
MB1C Other Goods Receipts
ME49 Price Comparison List
ME1E Quotation Price History
ME48 Display Quotation
ME4M Purchasing Documents for Article
ME21N Create Purchase Order
ME28 Release (Approve) Purchasing Documents
MB01 Goods Receipt for Purchase Order
ME2L Display Purchasing Documents per Vendor
ME23N Display Purchase Order
SPRO Maintain Rounding Profile
MD03 Single Item, Single Level
MD04 Stock/Requirements List
RWBE Stock Overview
WLB13 Automatic Load Building
WLB4 Results List for Automatic Load Building Run
WLB5 Bundle multiple orders logically
ME63 Calculate Scores for Semi-Automatic and Automatic Subcriteria
ME61 Maintain Vendor Evaluation
ME64 Evaluation Comparison
ME65 Ranking List of Vendors
ME6B Ranking List of Vendor Evaluations Based on Material/Material Group
R23 Fresh Items Procurement
Transaction code transaction text
SU3 Maintain User Profile
WDBI Assortment List: Initialization and Full Version
WDFR Perishables Planning
MB1C Other Goods Receipts
MIGO Goods Receipt Purchase Order
WF30 Merchandise Distribution: Monitor
VL06O Outbound Delivery Monitor
MB0A Goods Receipt-PO Unknown
WDFR Perishables Planning
VL10B Fast Display Purchase Orders,
MB01 Post Goods Receipt for PO
RWBE Stock Overview
ME61 Maintain Vendor Evaluation
ME63 Calculate Scores for Semi-Automatic and Automatic Subcriteria
MEKH Market Price
ME64 Evaluation Comparison
ME65 Ranking List of Vendors
ME6B Ranking List of Vendor Evaluations Based on Material/Material Group
R25 Subsequent Settlement
Transaction code transaction text
SU3 Maintain User Profile
MEB3 Display Rebate arrangement
MEU2 Perform Comparison of Business Volumes
MEB4 Create Settlement Document Via Report
MEB3 Create Service Notification-Malfn.
MEB1 Create Agreement
ME21N Create Purchase Order
MB01 Goods Receipt for Purchase Order
ME81 Analysis of Order Values
MIRO Enter Invoice
MEB8 Detailed Settlement
SECATT Generating business volume with CATT
SECATT Generating business volume with CATT
R26 Invoice Verification
Transaction code transaction text
SU3 Maintain User Profile
ME21N Create Purchase Order
MB01 Goods Receipt for Purchase Order
ME81 Analysis of Order Values
MIRO Enter Incoming Invoice
MIR4 Display Invoice Document
MIR7 Park Invoice
MIRA Enter Invoice for Invoice verification in Background
WC23 Invoice Verification-Background Check
MRRL Evaluated Receipt Settlement (ERS)
ME22N Retroactive Price Changes in Purchase Order
MRNB Revaluation with Log. Invoice Verification
MIR6 Invoice Overview-Selection Criteria
MRBR Release Blocked Invoices
R31 Sales Order Management
Transaction code transaction text
SU3 Maintain User Profile
VV32 Change Export Billing Document
VV31 Create Export Billing Document
MB1C Enter Other Goods Receipts
ME21N Create Purchase Order
VV32 Change Export Billing Document
RWBE Stock Overview
VV31 Create Export Billing Document
VA01 Create Sales Order
MM42 Chang Article
VA03 Display Sales Order
RWBE Stock Overview
VL01N Enter Other Goods Receipts
LT03 Create Transfer Order for Delivery Note
LT12 Confirm Transfer Order
ME5A Displaying Purchase Requisition
ME81 Analysis of Order Values
MIRO Enter Invoice
VA02 Change Sales Order
SECATT Backorder Processing
WFRE Distribution of Returns Among Backorders
V_V2 Rescheduling sales and stock transfer documents
VA05 List of Sales Order
V_R2 Rescheduling of sales and stock transfer documents
SECATT Generating Processing Document(s) via CATT
VF01 Create Billing Document
VF05 List of Billing Documents
VF02 Change Billing Doc
VF04 Maintain Billing Due List
V.21 Log of Collective Run
F-29 Post Customer Down Payment
F-39 Clear Customer Down Payment
VL02N Outbound Delivery Single Document
VF31 Output from Billing
MB1B Enter Transfer Posting
VL06O Outbound Delivery Monitor
VBO3 Displaying the Status of Rebate Agreement
VBO2 Settlement of the Agreement
VBO1 Creating Rebate Agreement
VBOF Update Billing Documents
LT03 Create Transfer Order for Delivery Note
LT12 Confirm Transfer Order
VA02 Releasing Credit Memo Request for the Partial Rebate Settlement
VL01N Create Outbound Delivery with Order Reference
VA01 Create Sales Order
VA03 Display Sales Order
VA41 Create Contract
VA43 Display Contract
CV01N Create Document
MM42 Chang Article
MM43 Display Article
WWM1 Create product catalog
XD02 Customer Display
OVKK Define Pricing Procedure Determination
SPRO Maintain Pricing Procedures
WWM2 Change Product Catalog
WAK2 Promotion Change
R32 Instore Customer Relationship Management
Transaction code transaction text
SU3 Maintain User Profile
SICF HTTP Service Hierarchy Maintenance
ME5A List Display of Purchase Requisitions
ME21N Generating a Purchase Order on the Basis of the Purchase Requisition
MIRO Entering an Incoming Vendor Invoice
VF01 Create Billing Document
VF02 Change Billing Doc
R33 Service - Return ProcessingTransaction code transaction text
SU3 Maintain User Profile
WPMI POS Outbound:Initialization
WPMA Direct request for POS ountbound
WPER POS Interface Monitor
WPMU Creating Change Message
WE02 Displaying Created IDocs in POS Monitor
MM42 Chang Article
VD02 Customer Change
WB60 Creating Site Group
WB66 Maintain Assignment of Sites
WAK1 Create promotion
WE02 Displaying Idoc
WDBI Initialization and Full Version
WDBM Manual Selection Assortment List
RWBE Stock Overview
MB1C Other Goods Receipts
WPUK POS Simulation:Selection
WPUF Cash Removal
FB03 Displaying Accounting Document
FAGLL03 Displaying Clearing Account
WPCA Execute Settlement
F-06 Post Incoming Payments:Header Data
WVFB Simulation Store Orders:Header Data Selection
WE02 Displaying Confirmation Order
VL10B Fast Display Purchase Orders,
VL02N Outbound Delivery Single Document
WPUW Goods Movements
MB0A Returning Goods to Vendor
MB1B Posting Goods to Unrestricted Use
ME23N Displaying Purchase Order
MIRO Invoice Verification
WR60 Replenishment:Parameter Overview
ME27 Create Purchase Order
WRP1 Replenishment:Planning
VL02N Change Outbound Delivery
LT12 Confirm Transfer Order
RWBE Stock Overview
WB02 Site Change
MB1C Enter Other Goods Receipts
MI01 Create physical inventory document
MI31 Selected Data for Phys. Inventory Docmts W/O Special Stock
MI02 Change physical inventory document
WVFD Send physical inventory document
WVFI Simulation:Store Physical Inventory/Sales Price Change
MI03 Display physical inventory document
MI20 List of Inventory Differences
MIDO Display Physical Inventory Overview
WPUW Goods Movements
WPUS Simulation:Inbound Processing
WE19 Test tool for IDoc processing
MM41 Create Article
VBG1 Create Article Grouping
VBK1 Create bonus buy
R34 Store Business online
Transaction code transaction text
SU3 Maintain User Profile
SICF HTTP Service Hierarchy Maintenance
WB02 Site Change
WSOA6 Assortment Assignment Tool
WSM8 Reorganize Listing Conditions By Merchandise Category
WDBI Assortment List:Initialization and Full Version
WA01 Create allocation table:Initial
WA08 Follow-On Document Generation Allocation Table
VL02N Change Outbound Delivery
WAK1 Create Promotion
WAK5 Promo. Subsequent processing
WPUK POS Simulation
MM42 Change Article
VL10B Fast display Purchase Orders
VL02N Change Outbound Delivery
WMBE Stock Overview
MB1C Enter Other Goods Receipts
VKP1 Change Price Calculation
VKU6 Revaluation at Retail
R35 Promotion Management
Transaction code transaction text
SU3 Maintain User Profile
RWBE Stock Overview
MB1C Enter Other Goods Receipts
WB60 Creating Site Group
WB66 Maintaining Site Group
WA21 Allocation Rule Create
WAK1 Create promotion
WAK5 Promo. Subsequent processing
WAK2 Change Promotion
WA08 Follow-On Document Generation Allocation Table
VL06O Outbound Delivery Monitor
MB0A Goods Receipt-PO Unknown
WAK15 Promotions per Site
WAK14 Promotions per article
VA01 Create Sales Order
VL01N Create Outbound Delivery with Order Reference
VL06P Outbound Deliveries for Picking
VL06C Confirming Transfer Order and Post Goods Issue
VL03N Display Outbound Delivery
VF01 Create Billing Document
R41 Distribution Center Logistics with Lean-WM
Transaction code transaction text
ME21N Create Purchase Order
VL31N Creating Inbound Delivery
WAP2 Create Purchase Order
VL41 Create Rough Goods Receipt
WAP2 Create Purchase Order
MB0A Goods Receipt PO Unkown
MB03 Display Article Document
MBRL Enter Return Delivery
MB02 Change Article Document
MB90 Output from Goods Movements
VL01NO Create Output Delivery Without Order Reference
LT03 Create Transfer Order for Delivery Note
LT12 Confirm Transfer Order
VL02N Posting Goods issue
VL01NO Create Outbound Delivery Without Order Reference
VL35 Create Piching Waves According to Delivery Compare Times
VL06P Outbound Deliveries for Picking
LT42 Create TOs by Mult.Processing
LT25N Transfer Order for Each Group
VLSP Subsequent Outbound-Delivery Split
VL06G Outbound Deliveries for Goods Issue
MI01 Create physical inventory document
MI31 Selected Data for phys.Inventory Docmts W/o Special Stock
MI04 Enter inventory count
MI20 List of Inventory Differences
MIDO Display Physical Inventory Overview
VL06O Outbound Delivery Monitor
VL37 Wave Pick Monitor
VLLG Rough Workload Estimate
R42 Distribution Center Logistics With Lean Warehouse Management
Transaction code transaction text
SU3 Maintain User Profile
RWBE IM Stock Overview
LS26 WM Stock Overview
SPRO Assign Processor to Queues
ME21N Create Purchase Order
VL31N Creating Inbound Delivery
WAP2 Create Purchase Order
VL41 Create Rough Goods Receipt
MB0A Goods Receipt PO Unknown
LT06 Create Transfer Order for Article Document
LT12 Confirm Transfer order
LRF1 Resource Planning with the RF Monitor
LM00 Mobile Data Entry
LRF1 Monitoring with the RF Monitor
MB03 Display Article Document
MBRL Enter Return Delivery
MB02 Change Article Document
MB90 Output from Goods Movements
LB12 Process Article Document
LP21 Replenishment for Fixed Bins in WM
LB10 Display Transfer Requirement: List for Storage Type
VL01NO Create Outbound Delivery Without Order Reference
LT03 Create Transfer Order for Delivery Note
LRF1 Resource Planning in the Monitor for Mobile Data Entry
LRF1 Monitoring from the Mobile Data Entry Monitor
VL02N Posting Goods Issue
VL35 Create Picking Waves According to Delivery Compare Times
VL06P Outbound Deliveries for Picking
LT42 Create TOs by Mult. Processing
LT25N Transfer Orders for Each Group
VLSP Subsequent Outbound-Delivery Split
VL06G Outbound Deliveries for Goods Issue
LX16 Carry out Continuous Inventory
LI11N Enter Inventory Count
LI14 Start Recount
LI20 Clear Differences in WM
LI21 Clearing of differences in Inventory Management
LX18 Statistics for Inventory Differences
LX25 Inventory status
LL01 Warehouse Activity Monitor
VL06O Outbound Deliveries for Picking
VL37 Wave Pick Monitor
VLLG Rough Workload Estimate: Total Overview
R43 Merchandise Distribution
Transaction code transaction text
SU3 Maintain User Profile
ME21N Create Purchase Order
ME31K Create contract
WA21 Allocation Rule Create
WA01 Create Allocation Table
WA11 Allocation Table Message Bundling / Notification Creation
WA04 Create Notification
WA08 Create Follow-On Documents
MB01 Goods Receipt for Purchase Order
WF10 Create Collective Purchase Order
MB01 Create Purchase Order
WF30 Adjusting Distribution and Generating an Outbound Delivery
VL06O Outbound Delivery Monitor
VL02N Outbound Delivery Single Document
WF50 Adjusting Distribution
WF70 Creating Distribution Order
LT23 Display Distribution Order
WF60 Generating Outbound Delivery
WA01 Create allocation table:Initial
R50 ECR-Compliant Procurement Processes
Transaction code transaction text
PRICAT Initial Screen: Price Catalog Maintenance
PRICATCUS1 Change View "Assignment of ILN-Vendor-Purchasing group": Overview
PRICATCUS2 Change View "Assignment of ILN-merch.catgry-SAP merch.catgry": Ove
PRICATCUS3 Change View "Assignment of SAP merchandise category - purchasing group"
WE19 Test tool for IDoc processing
WE20 Partner profiles
ME21N Create Purchase Order
WE02 Idoc list
ME23N Display Purchase Order
MB0A Goods Receipt - PO Unknown: Initial Screen
MIR4 Display Invoice Document
WVM2 Transfer of Stock and Sales Data
Regards,
ManiKumaar

RETAIL in SAP

Hi Bw Experts,
Can any body send me the detailed document for "Retail". we are going to start new project for retail in SAP. so pls send me urgently. don't send me the links.
E-mail: [email protected]
Thanks in advance
DORA

Hi Dora,
Revaluation at Retail
http://help.sap.com/saphelp_nw04/helpdata/en/8e/65f438c842cc2be10000000a114084/content.htm
BW SAP Retail
http://help.sap.com/saphelp_nw04/helpdata/en/86/39d6386e24f90ae10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/73/d26594107711d4af1e080009d2232d/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/35/e58282fe8711d3b49f006094b9301e/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/39/e531c93747da4a8806612212b013b4/content.htm
You will get some more info from www.service.sap.com/bi -->>solution detail -->>Industry Portfolios -->> Sap Retail
http://service.sap.com/bi
Bye
Dinesh

BI Best Practices for Customization

Dear Experts,
When I am developing BI reports by using mix of Standard BI Content and customized datasources at R/3 side.
In Standard BI Content also I am adding additional columns whereever required.
Now at BI side since I am changing structure/Update rule of cube/ODS, I am copying standard one to Z one.
If I want to make some InfoObjects as Authorization relevant I am copying it and changing that instead of changing original one.
I copied 0SALES_DIST to ZSALESDIS and made it Auth relevant, but I am able to use stadard DS for text (0SALES_DIST_TEXT) in ZSALESDIS which is already used in 0SALES_DIST.
I copied 0CUST_GROUP to ZCUSTGRP and added one attribute to it. I am not able to use 0CUST_GROUP_TEXT in ZCUSTGRP. I intend to use same DS.
0CUST_GROUP is Nav Attr in 0SOLD_TO so I have to copy 0SOLD_TO and use that customized in all my InfoProviders.
Even if I do that I am worried that there will be duplicate data for small small changes.
Can you please help me how to copy and customize the data model without disturbing standard data models.
Regards,
Tech Cheta

Hi,
BW SAP Retail
http://help.sap.com/saphelp_nw04/helpdata/en/86/39d6386e24f90ae10000000a114084/content.htm
Revaluation at Retail
http://help.sap.com/saphelp_nw04/helpdata/en/8e/65f438c842cc2be10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/73/d26594107711d4af1e080009d2232d/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/35/e58282fe8711d3b49f006094b9301e/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/39/e531c93747da4a8806612212b013b4/content.htm
www.service.sap.com/bi -->>solution detail -->>Industry Portfolios -->> Sap Retail
http://service.sap.com/bi
http://help.sap.com/content/documentation/industry/docu_is_retail.htm
http://help.sap.com/content/documentation/industry/docu_is_retail_retail.htm
http://help.sap.com/content/bestpractices/industry/bestp_industry_retail.htm
Hope this helps,
Regards
CSM reddy

BAPI for VKU2?

Hi guys! I have tried to search a BAPI for transaction VKU2 (Total revaluation at retail on posting date) but I found nothing. There is a business object SAP40319
for retail revaluation but has no method yet for posting the revaluation. If anyone nows which FM should I used, let me know, else I will create a BDC,
this is a difficult one!
thanks
Alex

Hi,
Please try in the following exit:
EXIT_SAPLWBW2_001
reward if helpful.

Fill Setup tables

Hello Experts,
What is the transaction code to fill MC40RP0REV setup table(Revaluation at retail)
Thanks
Fazal

Its ORISBW

Can anyone tell me where to see OSS notes

Hi
Can anyone tell me where to see composite OSS note 586163 (any OSS notes). In which site and in which category i should search.

www.service.sap.com
SAP Support Portal
Quick Lnks :
Search for OSS notes.
You need to have a login..its not free.
After login - Help & Support - Search for SAP notes
<b>
Anyws here is the note</b>
Summary
Symptom
You are transferring data from SAP R/3 Inventory Management to the BW system. You get unexpected data or data that differs from the data in the analyses in the R/3 system.
This note should help you to analyze this problem.
Other terms
2LIS_03_BF, 2LIS_03_UM, 2LIS_03_BX, 2LIS_40_S278, 2LIS_03_S195,
2LIS_03_S196, 2LIS_03_S197, 2LIS_03_S198, 0IC_C01, 0IC_02, 0IC_C03,
0IC_MC01, 0IC_MC02, 0IC_MC03, stock analyses, inventory management,
Non-cumulative InfoCubes, stock key figures, stock, stocks,
RMCBINIT_BW, RMCBNERP, RMCBNEUA, consistency,
data consistency, healthcare, health service
Reason and Prerequisites
This note provides an overview of the release strategy, sources of information, tips and tricks, and known errors for this subject area.
Solution
Contents
1. Release strategy
a) General information
b) Recommended objects for BW Releases 3.0B, 3.1 Content and 3.2 Content
c) Recommended objects for BW Releases 2.0B and 2.1C
d) Obsolete objects
e) Queries/Web templates of the 0IC_01, 0IC_C02 and 0IC_C03 InfoCubes
2. Sources of information
a) BW technology
SAP BW online documentation
"How to" documents
b) Business Content
Online documentation for BI Content
Extraction Documentation:
"How to" documents
Plug-In information
3. Extracting non-cumulative data from R/3
a) Explanations for the extraction
b) Known errors
Stocks (2LIS_40_S278/2LIS_03_BX)
Movements and revaluations (2LIS_03_BF and 2LIS_03_UM)
Industry-specific notes
4. Technical information regarding non-cumulative info cubes in BW
a) Warehouse Management
b) Queries
c) Update rules
d) Known errors
5. Stock Analyses in BW
a) Explanations on data flow
b) Known errors
c) Tips and tricks
6. Performance
1. Release strategy
Use the following objects depending on your BW and R/3 or plug-in releases:
a) General information
The following basic principle applies: The 0IC_C03 InfoCube (material movements) replaces the 0IC_C01 (material movement plant) and 0IC_C02 (material movements storage location) InfoCubes. The 2LIS_03_BX (material stocks) InfoSource or DataSource replaces the 2LIS_40_S278 (transfer BW: stock) 2LIS_03_S197 (material stocks storage location) and 2LIS_03_S198 (material stocks plant) InfoSource or DataSource. The 2LIS_03_BF (material movements) InfoSource or DataSource replaces the 2LIS_03_S195 (material movements storage location) and 2LIS_03_S196 (material movements plant) InfoSource or DataSource.
We therefore STRONGLY recommend that you use the OIC_C03, 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM objects. We will continue to deliver and support any other objects mentioned in this note, but only for reasons of downward compatibility. These objects will not be enhanced because they are based on obsolete technology.
For information about the general support for DataSources based on information structures, see also Note 543002.
As of PI 2002.2, the 2LIS_03_BX DataSource is available for Release 4.0B and higher.
As of PI 2001.2, the 2LIS_03_BF and 2LIS_03_UM DataSources are available for Release 4.0B and higher.
The 0IC_C03 InfoCube is available as of Release 3.0B.
b) Recommended objects for BW Release 3.0B and higher
InfoCube: 0IC_C03 (Material movements)
InfoSources and update rules:
2LIS_03_BX (stocks) - available for Release 3.0B as of Support Package 10
2LIS_03_BF (movements)
2LIS_03_UM (revaluations)
If your Support Package version for Release 3.0B is Support Package 9 or lower, you have the alternative option of using the 2LIS_40_S278 InfoSource or DataSource. However, for the reasons stated above, we recommend that you change to 2LIS_03_BX as of Support Package 10. For more information, see Note 588015.
c) Recommended objects for BW Releases 2.0B and 2.1C
InfoSources: 2LIS_03_BX (stocks) - available for Release 2.0B as of Support Package 30
                                - available for Release 2.1C as ofSupport Package 22
            2LIS_03_BF (movements)
            2LIS_03_UM (revaluations)
If you are using Release 2.0B Support Package 29 or lower or Release 2.1C Support Package 21 or lower, you can alternatively use the 2LIS_40_S278 InfoSource or DataSource. However, for the reasons given above, we recommend that you change to 2LIS_03_BX as of Support Package 30/Support Package 22. For more information, see Note 588015. Unfortunately, we cannot provide the 0IC_C03 InfoCube and related update rules. If you need to use this InfoCube, we can provide a similar solution to the one provided for Releases 3.0B or higher as part of a consulting project. Note that Note 589024 does not apply in this case.
d) Obsolete objects
If you are using R/3 Release 3.1I and do not intend to upgrade to a higher release (regardless of the BW release) in the foreseeable future, use only the 0IC_C01 and 0IC_C02 InfoCubes and the related InfoSources or DataSources 2LIS_03_S195 - 2LIS_03_S198. If you are using the Healthcare industry solution and are interested in using the 0IC_C01_Q0020 and 0IC_C01_Q0021 queries, you can also use the 0IC_C01 InfoCube and related objects. Unfortunately, there is no automatic data migration for the transition from 0IC_C01/2 to 0IC_C03. See also Note 804781 for a complete overview of all key figures in 0IC_C03 that are also possible in 0IC_C01/2.
e) Queries/Web templates of the 0IC_01, 0IC_C02 and 0IC_C03 InfoCubes
For more information, see Note 591063.
2. Sources of information
The main sources of information are located in the BW online documentation in the BW section of the SAP Service Marketplace and in the IMG documentation for the Plug-In. Other useful information is contained in various notes. These notes are listed under headings 3 - 6 below.
a) BW technology
This area contains documentation on the technical mapping of stock analyses in SAP BW.
Online documentation SAP BW (http://help.sap.com)
-> Documentation -> SAP NetWeaver -> '04
-> Information Integration -> SAP BW
i Stocks
    -> BI Platform -> OLAP
    -> Performance Optimization -> Stocks
ii Validity Table
    -> Data Warehousing
    -> Administrator Workbench -> Modeling -> InfoCube
    -> Additional functions for InfoCube maintenance
    -> Stock Parameter Maintenance
iii Compression
    -> Data Warehousing
    -> Administrator Workbench -> Data Warehouse Management
    -> Process Management
    -> Managing Data Targets
    -> Managing InfoCubes -> InfoCube Compression
iv Aggregation
    -> Data Warehousing
    -> Administrator Workbench -> Modeling
    -> InfoObject -> Create InfoObject: Key Figure
    -> Aggregation v Exception Aggregation
    -> BI Platform -> OLAP
    -> Special OLAP Functions and Services
    -> Aggregation
    -> Scenarios for the Use of an Exception Aggregation
"How to" documents
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> In the information index: N ("Non-cumulatives") ->
"Non-Cumulative Values 3.x (ppt)"
b) Business Content
This area contains the business content representation of stock analyses in SAP BW, based on the SAP R/3 process and object model.
Online documentation for BI Content (http://help.sap.com)
-> Documentation -> SAP NetWeaver -> '04
-> Information Integration: BI Content
-> BI Content -> Supply Chain Management
-> Supply Chain Performance Management -> Inventory Management
Documentation for extraction (OLTP system)
-> Transaction SBIW
-> Business Information Warehouse
-> Settings for application-specific DataSources
-> Logistics
Here you will find the relevant documentation for each of the relevant nodes.
"How to" documents
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> in the information index: N ("Non-cumulatives") ->
"How to... Handle inventory management scenarios in SAP BW 3.x" (pdf)
Plug-In information
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW Extractors - Plug-in
3. Extracting non-cumulative data from R/3
This section explains the extraction process in the R/3 system and it gives an overview of known errors and their solutions.
a) Explanations for the extraction
Determining transaction keys
Note 492828
Determining the component
When stocks are initialized, the 'MM' core application is transferred, regardless of which component you specify in Customizing under 'Specify Industry' (TAC MCB_). You must implement Note 323018 for this purpose.
In most cases, the 'MM' Core application is also used when you initialize documents and for the delta load. However, 'IS-R' is transferred as the component if Retail is set as the component and you are working with stock transfers or movements for material group articles (MATNR <> MATBF).
To create the component, the BW enrichment is required during extraction. For more information, see Notes 315880 and 353042.
The "GETSYSDEF" report provides the system setting.
Creating non-cumulative relevance
In general, the non-cumulative relevance is set to '1', meaning 'relevant'. The exceptions are consumption postings (BSTTYP = V and BSTAUS = V) and postings for material group articles (MATNR <> MATBF). Value '2' is assigned in these cases.
Logistics data extraction: Customizing Cockpit (transaction LBWE)
You can configure the 2LIS_03_BF und 2LIS_03_UM DataSources in application 03. You cannot configure the 2LIS_03_BX DataSource in the Customizing Cockpit. To activate the 2LIS_03_BX DataSource, see Note 631345.
Generic extraction of stocks
This function is available as of PI 2003.1. For lower release levels, a consulting solution can be implemented on request (contact SAP in this case).
User exit (SAP enhancement RSAP0001)
Note 413807
Update methods/extract structures/XPRAs
i Update methods (V3 update, DeltaQueue, and so on).
Notes 380078, 396647, 486784 and 505700.
For information about the automatic conversion of update methods in the logistics extraction, refer to the release notes for plug-in 2003.1
DataSources for application 03 are delivered by default with the "Unserialized V3 Update" method.
A change to "Queued Delta" may occur.
For performance reasons, you should not select "Direct Delta".
ii Changes to extract structures/XPRAs
Notes 328181, 489259, 511657 and 566917.
If you try to add another field from the pool to the "2LIS_03_BF" DataSource , the system issues error message "D0 322".
Possible reason:
XPRA "RMCSBWXP_IM_01" did not run after you imported the plug-in. This XPRA is responsible for comparing customer fields in the extract structure (enhancement) with new default fields in the extract structure (SAP). This error message appears as a result.
b) Known errors
Stocks, movements and revaluations are transferred to BW using various extractors. All known errors and proposed solutions of these three extractors are listed below.
Stocks (2LIS_03_BX/2LIS_40_S278) -> see Note 691228.
i Rounding error/valuation at company code level
    Notes 663681 and 762219
ii Project stocks
    Note 535657
iii Valuated sales order stocks or project stocks
    Notes 487043, 616119, 674351 and 756151
iv Vendor consignment stocks
    Notes 585619 and 726485
v Special stocks for customers/vendors
    Note 533682
vi Valuation class
    Note 684789
vii Stock in transit
    Notes 767786 and 898231
Movements and revaluations (2LIS_03_BF and 2LIS_03_UM)
i Delta ability/procedure
    Notes 385703 and 581778
ii Update methods (V3 update, delta queue, qRFC and so on)
    Notes 339691, 444261, 498484 and 631562
iii Missing BW derivation (component,
    transaction key, and so on)
    Notes 315880 and 353042
    Caution: You MUST read these notes
    BEFORE you transfer data to the BW system.
iv Movements (2LIS_03_BF)
    - Returnable packaging with customer
      Notes 512597 and 530730
    - Vendor consignment
      Notes 585139 and 607710
    - Project stocks
      Note 522770
    - Stock transfers
      Notes 399929, 557378 and 628090 (stock in transit/
      valuation type)
    - Purchase orders with account assignment (consumptions)
      Notes 587320 and 629726 (non-valuated materials,
      see also Notes 752607 and 790506)
    - Batches
      Notes 445632 and 685450
    - Incorrect stock type
      Notes 438649 and 451355
    - Customer consignment
      Note 563342
    - Incorrect / missing valuation class
      Notes 735425, 747581 and 770858
    - Returns (movement types 122/123)
      Notes 741396 and 763424
    - Profit center
      Note 769660
    - Subsequent adjustments
Note 822396
v Revaluations (2LIS_03_UM)
    - Incorrect update because the
      BSTAUS and BSTTYP fields are missing
      Notes 494288 and 675610
    - Missing BW derivation of characteristics with settlement ofrequests
      Notes 523298 and 747361
    - External display of the WBS element does not exist
      Note 512611
    - Incorrect transaction key during setup
      Note 587241
    - Incorrect sign
      Note 587283
    - Duplicate document for MR22
      Note 587304
    - Incorrect/missing document number
      Notes 489290, 500825, 507958, 521046, 619482,
              667534, 739050, 839711, 845307, 856669 and
              864630
    - The BUZEI field is not filled
      Note 599731
    - Currency field not filled
      Note 612131
    - Returns (movement types 122/123)
      Note 715176
    - Reconstruction report RMCBNERP
      Note 735209
    - Missing valuation class
      Note 837052
vi Master data (0STOCKTYPE/0STOCKCAT)
      Note 766954
    - 0STOCKCAT_TEXT is not filled since the value 'U' has not been added to the BSTTYP domain.
      Note 907195
Industry-specific notes
i IS Retail
- Revaluation at retail (2LIS_40_REVAL)
Notes 533577 and 600460
- Miscellaneous
Note 841878
ii IS Oil/IS Mine
- G/L quantity for two-step stock transfer procedure
Notes 608744, 608975 and 629320
4. Technical information regarding non-cumulative info cubes in BW
In addition to the relevant sections in the online documentation, there are a number of explanatory notes that will help you to analyze problems. Section 4 e) deals with known errors and proposed solutions.
a) Warehouse Management
Validity table: Notes 360249 and 534865
Selective deletion: Note 510680
Aggregates: Note 456359
ODS capability: Notes 322303, 323811, 385099, 417703, 581778,
747037, 752492/782314 and 773823
DataMart/Open Hub capability: Notes 375098, 566145 and 566762
Compression (updating the stock marker)
->>> ESSENTIAL INFORMATION <<<-
You can see in the log whether or not the stock marker was updated during the compression (as of 3.0B Support Package 13)
For example:
"START cond CUBE IC11 at 165446 on 20030514 maxreqid 23282 maxcnsid 0 refpoint update + null elim" ->
"refpoint update" or "no refpoint update" provides the relevant information.
See Notes 613701 and 639253 if you are using Oracle 9.
Also see Notes 643687 and 655798.
For a BW system with several application servers, see also Note 834829.
->>> ESSENTIAL INFORMATION <<<-
b) Queries
-> For information about the recommended procedure for analyzing query problems see the following note: Note 370004
Slow-moving item/slow seller reports: Note 541559
A How to document is also available:
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> in the information index: M ("MultiProviders") -> "MultiProviders (incl. Slow Moving Item Scenario) ..."
c) Update rules
The following special features are provided for updating in non-cumulative cubes:
The non-cumulative key figure has to be included with the relevant cumulative value(s) in the InfoCube definition.
Only receipt key figures are provided for updating from the InfoSource with the stocks.
The issue and receipt key figures are provided for updating from the InfoSource with movements.
Therefore, from a technical point of view, stocks are written to the receipt key figure. The process of differentiating between the stocks and the remaining receipts then takes place in the InfoCube using record type = 1 (InfoObject: 0RECORDTP) in the technical dimension table (this also sets up the connection to the validity table).
The OLAP processor dynamically calculates non-cumulative key figures in the query (taking into account the issues/receipts and the validity table).
d) Known errors
Warehouse Management
i Loading data
     Notes 534865 and 529610
ii MultiCube/MultiProvider
    Note 435227
iii Compression (updating the stock markers)
    Notes 613064, 613701 and 615349
iv Updating
     Note 574341
Queries
i Fiscal year variant characteristic (0FISCVARNT, 0FISCPER
and 0FISCYEAR)
    Note 490067
ii Exception aggregations
    Notes 145630 and 607608
iii No/multiple time restrictions
     Note 388983
5. Stock Analyses in BW
This section explains the data flow in BW and provides an overview of known errors and their solutions. This section also explains certain limitations and workarounds for same.
a) Explanations on data flow
See the How to paper from Section 2 b)
"How to... Handle inventory management scenarios in SAP BW 3.x" (PDF).
Note that the 2LIS_03_UM can also be loaded before the 2LIS_03_BF.
You will find further information on the SAP Service Marketplace:
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW Business Content
-> SAP Supply Chain Management
-> Supply Chain Performance Management
-> In the navigation area on the left: Related Topics
-> Business Content
-> Inventory Management.
b) Known errors
0IC_C03
Notes 637927, 655798, 668085 and 710404
0IC_MC01
Note 664520
Queries
Notes 534429, 630034 and 676960
c) Tips and tricks
Analyses in BW with the storage location (0STOR_LOC) and stock characteristic (0STOCKTYPE) characteristics in the drilldown.
Solution: Note 589024 (see also Notes 201327, 322335, 456106, 506077 and 543188) and the How to document
-> http://service.sap.com/bw
-> In the navigation area on the left: Services & Implementation
-> HOW TO ... Guides -> Guide List for SAP BW3.0B/BW3.1 ->
"How to... Realize summarized display of stock values on storage"
Stock transfers in the two-step stock transfer procedure/differences between analyses in BW and the R/3 transaction MB5B
If you notice different results for the issue and receipt quantities of the total stock during the analysis of stock transfers in the two-step procedure, for example, storage location to storage location within a plant (movement types 351 and 101), add the "0STOCKTYPE" characteristic to the drilldown. Where necessary, filter according to the values "A" (unrestricted) and "H" (transit). You will then find the same values under stock type "A" and in transaction MB5B (if you select the storage location stock or the valuated stock).
Individual analysis of revaluations
After stock is initialized using the 2LIS_03_BX InfoSource, load revaluations into the 0IC_C03 InfoCube with the 2LIS_03_UM InfoSource. By doing this, you avoid uploading movements with the 2LIS_03_BF InfoSource. If you do so, the non-cumulative values (quantities and values) can no longer be calculated. Reason: When you initialize stocks, DIM IDs are created for 0BASE_UOM and 0LOC_CURRCY. As a result, all stock markers for 0BASE_UOM have an entry other than ' '. With revaluations, only values are updated-all quantities and their units are updated with ' '. This means that you can no longer assign revaluations to the stock markers because the units of measure are inconsistent. Solution: Update the revaluations with quantities also, as you did for the values (the result for the quantities is always RESULT = 0).
Incorrect results if quantity key figures and value key figures are analyzed together.
For example, you only displayed quantity key figures in the current drilldown. If you now add value key figures, the quantity key figures are no longer calculated correctly (the reverse also applies). As in the case of individual analyses of revaluations, movements may not be assigned to the stock markers due to missing DIM IDs. As a result, stock cannot be recalculated correctly either. This should not usually occur when the 0IC_C03 InfoCube is filled with the 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM InfoSources (this is also the case with the other relevant Business Content InfoCubes, for example 0CP_IC_C1 or 0RT_C36/37). However, it may occur because of certain loading processes, for example. Solution: Update the quantities (or values) in the same way as the values (or quantities) (RESULT = 0 is always the result for the quantities or values). See Note 643291 for the 0CP_IC_C1 InfoCube.
Enhancing the 0IC_C03 InfoCube with additional characteristics
These additional characteristics must be updated from the 2LIS_03_BX InfoSource, as well as from the 2LIS_03_BF and 2LIS_03_UM InfoSources, only then can movements be assigned to stock markers (see the two preceding points).
The following enhancements are possible:
1. Valuation type (0VAL_TYPE)
Source field from 2LIS_03_BX/BF: BWTAR
2. Company code (0COMP_CODE)
Source field from 2LIS_03_BF/UM: BUKRS
3. Valuation area (0ID_VALAREA)
Source field from 2LIS_03_BX/BF/UM: BWKEY
4. Vendor (0VENDOR/0GN_VENDOR) - for vendor consignment stocks
Source field from 2LIS_03_BX/BF/UM: LIFNR
This is delivered with BI Content 3.3 Add-On (see SRM Business Content Online documentation).
5. Customer (0CUSTOMER) - for consignment stocks at customer
Source field from 2LIS_03_BX/BF/UM: KUNNR
6. Sales order (0DOC_NUMBER/0S_ORD_ITEM) - for sales order stocks
Source field from 2LIS_03_BX/BF: KDAUF/KDPOS
7. Project number (0WBS_ELEMT) - for project stocks
Source field from 2LIS_03_BX/BF: PS_PSP_PNR
8. Evaluation class (0VAL_CLASS)
Source field from 2LIS_03_BX/BF/UM: BKLAS (Note 684789)
Enhancement possibilities for 2LIS_03_BX:
Note that the 2LIS_03_BX DataSource cannot be extended in the same way as the 2LIS_03_BF DataSource, for example.
Only SAP can enhance this DataSource (Note 684789).
Other enhancements are no longer useful since fields, such as the movement type, G/L account or profit center do not in appear in the stock tables (for example, MARC and MARD) but only in the movement tables (for instance, MSEG).
Evaluation restrictions that occur as a result (similar to the two preceding points) can only be resolved by a data enhancement (for example, reading from a DataStore object with all material movements) subsequent to the extraction or by not using 2LIS_03_BX. In both cases, all material movements must exist in the source system. If this is not the case, you must read from the corresponding archive files for the extraction.
Changing the exception-aggregation of the stock key figures
There is a predefined exception aggregation for stock key figures (for example, "last value") in the key figure definition. If you want to override these in the query definition, proceed as follows:
-> Create a new calculated key figure.
-> Drag the relevant basic key figure to the formula area.
-> Choose "OK".
-> In the next window, choose "Extend >>".
-> Then, maintain the required exception aggregation and the reference characteristic.
Mapping FIFO logic
The data structures in the 0IC_C03 InfoCube allow FIFO logic to be mapped using the relevant query definitions. In this case, contact your SAP consultant.
Unexpected or negative stock values due to FI document summarization
If FI document summarization is activated for the MATNR field, revaluations (2LIS_03_UM) are transferred to BW without a material number. As a result, complete analyses are no longer possible at material number level. For more information, see Notes 36353 and 497992.
Options for the R/3 and BW data verification/consistency check
TAC MB5B <-> Queries 0IC_C03_Q???
(Stocks/movements R/3 <-> BW)
TACs MC.? <-> Queries 0IC_C03_Q???
(Inventory controlling LIS <-> BW)
Reports MBQUANT and RM07MMFI
(verification of the R/3 data)
Notes 739863 and 745788 provide additional information in this regard, as well as the options that exist to clean up data in BW.
With Note 766622 you can also create a LOG file for the extraction.
Archiving
See the corresponding "How to" document about archiving that is available on SAP Service Marketplace:
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> in the information index: A ("Archiving")
MultiProvider and non-cumulative key figures
Note 690475
Displaying the contents of the InfoCube with TAC "LISTCUBE"
Note 629451
Snapshot scenario
The "How to" document mentioned in section 2 b) "How to... handle inventory management scenarios in SAP BW 3.x" (pdf)" contains important information about the advantages and disadvantages of mapping stocks using a snapshot procedure.
Validity period of stocks
You can use transaction RSDV to determine the time period in which stocks can be calculated. This time period is determined automatically by the oldest and the most recent material movement. If you have a reporting requirement to display further stocks in the past, you can use the RSDG_CUBE_VALT_MODIFY report to manually change the time period.
Evaluations of cross-company code stock transfers.
Corresponding reports are currently not possible using the 2LIS_03_BX/BF/UM DataSources. For further information, see the following "How t"o document:
-> http://service.sap.com/bw
-> In the navigation area on the left: Services & Implementation
-> HOW TO ... Guides -> Guide List for SAP BW3.0B/BW3.1 ->
"How to... Report on cross company stock in transit", which allows you to carry out evaluations in BW similar to the ones in R/3 transaction "MB5T".
0IC_C03 data modeling
Due to the different characteristic value calculation for stock quantities and values, a MultiCube scenario ("sparse tables") is useful in this case, one InfoCube for quantities and one for values.
You can then execute common stock quantities, values and evaluations using queries on a MultiCube.
The 0IC_C03 InfoCube currently uses a key figure model (various specific key figures, such as inspection stock, stock in transit and so on). In this case, an account model is suitable:
- Three key figures: Stock quantity, stock value and valuated stock quantity (including the movement key figures)
- Based on stock instance/type, you can then limit the query to the special stock
- Advantage: Uses less database space
- Disadvantage: The load for the OLAP processor is higher and there is more work during the query definition, the other approach may also be more transparent for the end user.
Inventory management and ODS
ODS objects cannot admit any stock key figures (see Notes 752492 and 782314) and, among other things, they do not have a validity table, which would be necessary. Therefore, ODS objects cannot be used as non-cumulative InfoCubes, that is, they cannot calculate stocks in terms of BW technology.
In this connection, you should use the ODS technology only for:
- Document-related reporting or the Enterprise DataWarehouse layer based on the 2LIS_03_BX/BF/UM InfoSources (see Notes 581778 and 747037).
- The implementation of a snapshot scenario; see the How to document mentioned in section 2 b) for more information:
"How to... handle inventory management scenarios in SAP BW 3.x" (pdf)
Implement Note 773823 to be able to update the 2LIS_03_BX InfoSource to an ODS.
If you want to activate another ODS object for the 2LIS_03_BF and 2LIS_03_UM DataSources before the 0IC_C03 InfoCube, we recommend a parallel update.
However, if you want the InfoCube to be filled by a subsequent update from the ODS, take the following into account:
Documents that are entered after the stock initialization (CPUDT field > stock initialization key date) and are posted back to a period before the stock initialization (BUDAT field < stock initialization key date),
must be updated with a delta request in the InfoCube, because only these requests can be compressed with a stock marker update.
Therefore, mechanisms for which the movements are different before and after the stock initialization (as a result of restrictions on the posting date) are incorrect in this case. However, if you want to work with the requests in question, you must restrict the movements using the date of entry (CPUDT). Otherwise the stock evaluations will be incorrect due to the compression logic used.
The same problem occurs if documents are posted to the future (CPUDT field > stock initialization key date and BUDAT field > stock initialization key date).
Posting to a prior period and postings to the future
If you can post this type of material documents in the system, take note of the documents that caused the initialization run (transaction MCNB, or report RMCBINIT_BW)during the reconstruction in R/3 (transaction OLI1BW, or report RMCBNEUA):
1. BUDAT < stock initialization key date and CPUDT > stock initialization key date
You execute the report with a date restriction (for example, upper limit = key date of stock initialization) to avoid a posting block.
-> Postings to a prior period are selected by mistake.
-> Solution: You MUST set a posting lock (if this is not possible, it may help to select according to the document number).
2. BUDAT > stock initialization key date and CPUDT < stock initialization key date
Here the same applies as described under point 1, however, the documents are then missing in the setup table. You can still make restrictions according to the posting date but you must set a relatively high upper limit.
Consumption key figures in 0IC_C03 (the same as LIS reports)
See Note 804781.
Avoiding data inconsistencies, HASH solution.
See Note 838050 for more information.
Connection between transaction keys and reversals. See Note 352344 (and an example in Note 745788).
Suppressing the display of the previous period in the BEx Web Analyzer.
See Note 623944.
6. Performance
a) General BW/logistics extraction (TSV_TNEW_PAGE_ALLOC_FAILED/ SYSTEM_IMODE_TOO_LARGE)
Notes 409641, 417307, 419465, 548845 and 589997
b) Extraction 2LIS_03_BX
The recommended setting in the RMCBINIT_BW report for 'Number of data records per LUW' is 5000. Higher values may cause the following errors:
TSV_TNEW_PAGE_ALLOC_FAILED
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
TSV_LIN_ALLOC_FAILED
You can reduce an extremely long runtime by setting up the stock individually for each plant. For more information, see Note 728360.
When you run the report, the "Transfer Zero Stocks" option must NOT be active, because this will significantly increase the runtime.
This is no longer required as of Note 823951 (for more information, see Note 655798).
c) Extraction 2LIS_03_UM
Notes 537235 and 585750
d) Extraction 2LIS_03_BF
Note 454267
e) Warehouse
Due to the stock marker generation technology, it is normal for the E table to be larger than the F table in the non-cumulative InfoCubes.
As a result of the different updating of stock quantities and values (see Note 589024) required by the R/3 data model, movement data usually generates two entries in the F table.
To reduce the data volume of the 0IC_C03 InfoCube, you can distribute quantity and value key figures to two InfoCubes. As a result, the key figures have the same characteristic value update again. You can then use MultiCubes to execute common evaluations of quantities and values.
f) Queries
Notes 419490 and 784682
Message was edited by:
        Jr Roberto

No retail price available for material MMMM in master conditions

Hi All ,
When running transaction VKU6 to pickup and display price changes for retail price . I am getting this message.
"No retail price available for material <MMMM> in master conditions"
I have already maintained the condition record for retail prices , am not sure what does these Master Conditions refer to.
Kindly give some advice...
thanks!!

Hi
VKU6 is for retail Re-valuation, if you want re-valuation to be done based on retail sales price than MAP then you use this transaction and see the changes here for the stores you selected then you go to VKU7 for automatic revaluation. If you are getting such error means you must be using two step price calculation and ran re-valuation for DC, try using re-valuation for store and you don't get such errors.
Pre-requisite is you should have old and new retail sales price for stores, these prices to be maintained against master condition type like VKP0 and same to be assigned in the list field.
If you are objective is to see only change in sales price then you can use t code VKP2 / VKP3
Best Regards
Swami

Documentation on Retail Method of Accounting

Dear all,
can anyone help me out or provide me some document on Retail method of accounting (RMA).
Thanks in advance.

Within SAP Retail, SAP supports essentially three inventory valuation methods: cost method of accounting (CMA), retail method of accounting RMA), and extended retail method of accounting (ERMA).
CMA and ERMA are calculated in ERP (see values and units in table MBEW) with stock ledger reports provided in BI.
The RMA Stock Ledger sits in BI and takes goods movements and revaluations from ERP and POS to recalculate inventory according to an RMA formula. At the end of the period, adjustments -- the difference in ending inventory and COGS between CMA and RMA -- are posted into the general ledger so that the G/L reflects RMA results not the standard, ERP, CMA results. Standard RMA stock ledger reports are also offered in BI.
Additional information for RMA can be found in the online documentation here:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/47/189be0958c369be10000000a11466f/frameset.htm
Additional information about ERMA can be found here:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/7d/9c184c1dce4fe3a2738f6b1f06fcfd/frameset.htm

How to delete the Sites in SAP IS RETAIL

hello ALL,
can any one explain me how to delete the Sites in Sap Retail.
thanks in advance

Hello All,
Delete the plant / Site complete details and put in one transport and do the import & export.
Thanks.
Edited by: krishna cherry on Jul 26, 2010 3:28 PM

Free goods in Retail

Hi
These are scenario for Beverage business- mostly they have complicated promotion on free gifts which I think SAP ERP SD cannot cover it. I also check Promotion in retail and found out, if it's discount - it can handled but for free goods - there is similar to ERP Sales. If anyone can take a look at the below case and share with me whether IS-Retail can handle it or any idea how to handle it as now I can only think of custom development.
This is pretty much general scenario in Thailand, not only beverage but wholesales & distribution but I don't think SAP ERP can handle it smoothly.
1. Buy soda water size 10 oz regardless of soda taste (coke, orange, grape) for 1 pack (1 pack consist of 24 bottles) then get 1 bottle free.
2. Buy soda water size 10 oz regardless of soda taste for 1 pack, then get 1 bottle free - maximum at 2 sets.
3. Buy soda water either size 10 oz or 15 oz for 1 pack, get 1 bottle of 10 oz free
4. Buy soda water regardless of soda taste as set i.e. for every 36 packs of combine size 10 oz, 15 oz and 1 lt - get free items of 10 oz/15 oz for 2 bottles per pack and free item of 1lt for 1 bottle per pack
5. Similar to 4 with additional condition that 1 soda taste must be more than 50% - for example, it must be coke at least 50%
6. Sales quota - Buy 1 pack, get 1 bottle free - maximum 100 bottles for each customer
Please kindly share your experience or ideas. Thank you
Chanchana

HI,
1. Use txn VBK1 to create a bonus buy condition
2. In SAP Retail, we can create % Off Conditions, Absolute Off Conditions as standard promotion conditions, Special Price Conditions.
3. You can also can create Bonus Buy: Price, Bonus Buy: % Discount, Bonus Buy: Absolute Discount and Bonus Buy: Free Goods conditions.
For Example: Buy 4 Get 1 Free Article is a Bonus Buy condition. for this try In VBK1, use Discount Type BB04 to configure bonus buy.
For more information plz try this link http://help.sap.com/erp2005_ehp_03/helpdata/EN/40/c0e238f0d111d2adff080009d2232d/frameset.htm
Regards
GK.

Free Goods Promotions for Retail.

Hi SAP Retail Xperts.
Actually I am working with Promotions for retail industry, and I am using the transaction WAK1, in order to create them.
Our client, work with free goods (exclusive bonus quantity) and I can see that the WAK1 transaction has a view for that, but the Create Free Goods button IS NOT active.
Does anybody knows how could I active it. If it is active, I will be able to create a Free Goods exclusive bonus quantity from WAK1 transaction???.
Thanks in advance.
Manuel

Hi Machacon,
Create Promotion in WAK1.Enter Articles in fast entry tab,Quantity in
Quantity Planning tab,site groups in site group tab.Save your promotion.
Go to your newly created Promotion in change WAK2, now you go to Free goods tab
where you can see free goods button in active form.
Hope this help you.
Regards,
Mohanavel

Revaluation in Retail

Similar Messages

Maybe you are looking for