Stock Snapshot using APD

Hello all,
Overview
I have requirement to get monthly snapshot of stock for all Materials, Plants and other characteristic combination. "How to... Inventory guide" mentions about using snapshot ODS and then snapshot cube.
Analysis
I would like to avoid using "How to" and replace that with APD.
I would create a Query on 0IC_C03 infocube and then using APD Monthly I would create the snapshot recordset for all Materials, Plants and other characteristic combination .
I have already looked at various OSS notes including 751577 - APD-FAQ: Data source query.
Questions
1)Will Query as source work for APD work with large volumes of data?
2). If Yes is there is a limitation what volume of records with the Query using APD feeding to transactional ODS can be handled.Our client will have the one of the highest volumes of records?
At the moment we are on BW 3.5.
Please let me know if you have any experience and thought about this.
Thanks
TK

Hi Mansi,
Thanks for the reply.
Scenario : I have data in Standard DSO ,I want to send the data to CRM system from BI.
1 ) yes, I have seen the CRM icon in targets , but I am not able to connect both BI and CRM system, please let me know what transformations option should I use, because I donu2019t want to do any calculations here , just I want to transfer the data from BI to CRM.
2 ) I have clicked the DSO option in the T-code RSANWB , here I have selected the standard DSO (Drag and Drop) and selected the CRM icon , I have connected both by black arrow sign and Transfer Rule icon in the middle.
3 ) After drag and Drop the DSO , I have right click the DSO and selected properties ,here I am able to see the info objects (under Selected Char).If I right click the CRM icon (i can see the description name for CRM) and select Properties , it is asking log in ID and password to CRM server , after that I am able to see u201CDescription which I have givenu201D , u201CLogical Systemu201D and u201CData Targetu201D.
I donu2019t what to mention here in the options?
Thanks,
Nithi.
Pls guide me , if I have missed out any steps.

Similar Messages

Closing stock by using opening sock

Hi All,
I got opening stock by using this how can I calculate closing stock,pls help me.
REPORT   zhzl_material_analysis_gb LINE-SIZE 1000.
tables:mara,mseg,s034.
TYPE-POOLS: slis.
DATA: budat TYPE budat.
DATA: v_fieldcat TYPE slis_fieldcat_alv,
v_t_fieldcat TYPE slis_t_fieldcat_alv.
*Internal Tables for Opening Stock Calculation
DATA : BEGIN OF t_mbew OCCURS 0,
matnr LIKE mbew-matnr,
bwkey LIKE mbew-bwkey,
lbkum LIKE mbew-lbkum,
salk3 LIKE mbew-salk3,
END OF t_mbew.
DATA: BEGIN OF i_mbew OCCURS 0,
mblnr LIKE mseg-mblnr,
mjahr LIKE mseg-mjahr,
menge LIKE mseg-menge,
meins TYPE meins,
bwart LIKE mseg-bwart,
matnr LIKE mseg-matnr,
*REP werks as bwkey
bwkey LIKE mseg-werks,
shkzg LIKE mseg-shkzg,
dmbtr LIKE mseg-dmbtr,
zeile LIKE mseg-zeile,
smbln LIKE mseg-smbln,
smblp LIKE mseg-smblp,
sjahr LIKE mseg-sjahr,
kunnr LIKE mseg-kunnr,
mblnr1 LIKE mkpf-mblnr,
mjahr1 LIKE mkpf-mjahr,
budat LIKE mkpf-budat,
taxkd LIKE knvi-taxkd,
END OF i_mbew.
DATA: BEGIN OF i_mara OCCURS 0,
matnr LIKE mara-matnr,
matkl LIKE mara-matkl,
spart LIKE mara-spart,
END OF i_mara.
DATA: i_makt TYPE TABLE OF makt WITH HEADER LINE.
DATA: BEGIN OF i_collect OCCURS 0,
matnr LIKE mara-matnr,
bwkey LIKE mbew-bwkey,
menge LIKE bsim-menge,
dmbtr LIKE bsim-dmbtr,
END OF i_collect.
DATA: BEGIN OF i_op_stock OCCURS 0,
matnr LIKE mara-matnr,
maktx LIKE makt-maktx,
matkl LIKE mara-matkl,
bwkey LIKE mbew-bwkey,
menge LIKE bsim-menge,
dmbtr LIKE bsim-dmbtr,
spart LIKE mara-spart,
END OF i_op_stock.
*The Selection-Screen Construction
SELECTION-SCREEN: BEGIN OF BLOCK sel_block WITH FRAME.
PARAMETER: p_werks LIKE mseg-werks.
*PlantCompany Code
SELECT-OPTIONS : s_date FOR budat,
                 p_spart for mara-spart,
*Division
                 p_bukrs for mseg-bukrs .
SELECTION-SCREEN: END OF BLOCK sel_block .
START-OF-SELECTION.
PERFORM opening_stock.
PERFORM alv.
*FORM opening_stock *
*Calculates stock for date value in the low field of the *
*select-options.
FORM opening_stock.
CLEAR t_mbew.
SELECT * FROM mbew INTO CORRESPONDING FIELDS OF TABLE t_mbew
WHERE bwkey = p_werks .
SORT t_mbew BY matnr.
REFRESH i_mbew.
CLEAR i_mbew.
LOOP AT t_mbew.
i_mbew-matnr = t_mbew-matnr.
i_mbew-bwkey = t_mbew-bwkey.
i_mbew-dmbtr = t_mbew-salk3.
i_mbew-menge = t_mbew-lbkum.
APPEND i_mbew.
CLEAR i_mbew.
ENDLOOP.
SELECT
mseg~mblnr
mseg~mjahr
mseg~bwart
mseg~menge
mseg~matnr
mseg~shkzg
mseg~werks AS bwkey
mseg~zeile
mseg~smbln
mseg~smblp
mseg~sjahr
mseg~kunnr
mkpf~mblnr AS mblnr1
mkpf~mjahr AS mjahr1
mkpf~budat
FROM mseg AS mseg INNER JOIN
mkpf AS mkpf ON
msegmblnr = mkpfmblnr
AND
msegmjahr = mkpfmjahr
APPENDING CORRESPONDING FIELDS OF TABLE i_mbew
WHERE mkpf~budat > s_date-low
AND mseg~bukrs in p_bukrs
AND mseg~werks = p_werks
AND mseg~kzvbr = ' '
AND mseg~bustw NE ' '.
SORT i_mbew BY matnr budat mblnr.
SORT i_mara BY matnr.
SORT i_makt BY matnr.
LOOP AT i_mbew.
IF i_mbew-shkzg = 'S'.
i_mbew-dmbtr = i_mbew-dmbtr * ( - 1 ).
i_mbew-menge = i_mbew-menge * ( - 1 ).
ENDIF.
MODIFY i_mbew TRANSPORTING dmbtr menge.
ENDLOOP.
CLEAR i_collect.
LOOP AT i_mbew.
i_collect-matnr = i_mbew-matnr.
i_collect-bwkey = i_mbew-bwkey.
i_collect-dmbtr = i_mbew-dmbtr.
i_collect-menge = i_mbew-menge.
COLLECT i_collect.
ENDLOOP.
CLEAR: i_collect,i_op_stock.
LOOP AT i_collect.
MOVE-CORRESPONDING i_collect TO i_op_stock.
APPEND i_op_stock.
CLEAR i_op_stock.
ENDLOOP.
CHECK NOT i_op_stock[] IS INITIAL.
LOOP AT i_op_stock.
DELETE i_op_stock WHERE menge = 0.
ENDLOOP.
SORT i_op_stock BY matnr.
SELECT * FROM mara INTO CORRESPONDING FIELDS OF TABLE i_mara
FOR ALL ENTRIES IN i_op_stock
WHERE matnr = i_op_stock-matnr
AND spart in p_spart.
SELECT * FROM makt INTO TABLE i_makt
FOR ALL ENTRIES IN i_mara
WHERE matnr = i_mara-matnr
AND spras = 'EN'.
LOOP AT i_op_stock.
CLEAR i_mara.
READ TABLE i_mara WITH KEY matnr = i_op_stock-matnr.
IF sy-subrc = 0.
i_op_stock-matkl = i_mara-matkl.
i_op_stock-spart = i_mara-spart.
MODIFY i_op_stock TRANSPORTING matkl spart.
ELSE.
DELETE i_op_stock.
ENDIF.
ENDLOOP.
LOOP AT i_op_stock.
CLEAR i_makt.
READ TABLE i_makt WITH KEY matnr = i_op_stock-matnr.
IF sy-subrc = 0.
i_op_stock-maktx = i_makt-maktx.
MODIFY i_op_stock TRANSPORTING maktx.
ELSE.
DELETE i_op_stock.
ENDIF.
ENDLOOP.
ENDFORM.
FORM alv.
CLEAR v_fieldcat.
v_fieldcat-col_pos = 1.
v_fieldcat-fieldname = 'MATNR'.
v_fieldcat-seltext_m = 'Material code'.
APPEND v_fieldcat TO v_t_fieldcat.
v_fieldcat-col_pos = 2.
v_fieldcat-fieldname = 'MAKTX'.
v_fieldcat-seltext_m = 'Description'.
APPEND v_fieldcat TO v_t_fieldcat.
v_fieldcat-col_pos = 3.
v_fieldcat-fieldname = 'MATKL'.
v_fieldcat-seltext_m = 'Material Group'.
APPEND v_fieldcat TO v_t_fieldcat.
v_fieldcat-col_pos = 4.
v_fieldcat-fieldname = 'SPART'.
v_fieldcat-seltext_m = 'Division'.
APPEND v_fieldcat TO v_t_fieldcat.
v_fieldcat-col_pos = 5.
v_fieldcat-fieldname = 'BWKEY'.
v_fieldcat-seltext_m = 'Plant'.
APPEND v_fieldcat TO v_t_fieldcat.
v_fieldcat-col_pos = 6.
v_fieldcat-fieldname = 'DMBTR'.
v_fieldcat-seltext_m = 'Amount'.
APPEND v_fieldcat TO v_t_fieldcat.
v_fieldcat-col_pos = 7.
v_fieldcat-fieldname = 'MENGE'.
v_fieldcat-seltext_m = 'Quantity'.
APPEND v_fieldcat TO v_t_fieldcat.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
it_fieldcat = v_t_fieldcat
TABLES
t_outtab = i_op_stock.
ENDFORM.
Thanks&regds,
Sree.

Hi,
Please note that MBEW contains the stock position as of now. MBEWH contains the closing stock of all the previous periods. However if there is no transaction in a particular period you may not find a record in MBEWH for that period.
Please refer to SAP documentation:
[Back To Resultlist]
Material Master (Industry/Retail): Enhancements to Period Closing
Description
In Release 4.5A, the period closing function has been redesigned to eliminate or at least alleviate the following problems:
Long runtime if there are very many stock segments
Locking of all materials while the period closing program is run
Data inconsistencies in stock segments due to incorrect operation of the period closing program by users
The enhancements made to eliminate or alleviate these problems affect the way in which period closing is performed technically and particularly the data design. As a result, the following information is intended primarily for the following persons:
System administrators
Developers (for example, in customer projects)
Other persons in IT departments or systems departments
Runtime
The runtime of the period closing program has been improved substantially since no stock tables (such as MBEW, MARD, or MCHB) are updated any longer for the change in period, unless the change in period is a change in fiscal year. Only the material ledger tables are updated.
If the change in period coincides with the end of a fiscal year, the program also updates the physical inventory indicators and thus those tables relevant to physical inventory management; that is, even in this case, table MBEW in particular is no longer updated.
Locking of materials
The materials are locked by the period closing program only if the material ledger is used.
In the case of a change in fiscal year, no physical inventory transactions can be performed when running the period closing program.
Ease of use
As of Release 4.5A, period closing is performed in inventory management or invoice verification; that is, whenever, for example, a goods movement is made, the period is updated in the relevant stock segments of the material if the material is moved for the first time in this period.
Changes to the interface
There have been no changes to the interface.
Changes in procedure
The implementation of the above enhancements has required the data design to be changed as follows:
Stock tables MBEW, EBEW, QBEW, MARC, MARD, MCHB, MKOL, MSKA, MSSA, MSKU, MSLB, MSPR, and MSSQ now have history tables, for example, MBEWH is the history table for MBEW, and EBEWH the history table for EBEW. For each period, these history tables can contain an entry with the corresponding stock information, and are created for the previous period whenever there is a change in period-relevant information such as unrestricted-use stock. This means that the information for the previous period can no longer be read directly from tables MBEW, EBEW, and so on, but that tables MBEWH, EBEWH, etc. have to be read and interpreted.
The point in time at which the system is upgraded to Release 4.5A is important for interpreting the history tables. If the period has been closed at least once after the upgrade, the stocks for the previous period are contained, for example, in history table MARDH. If this table does not contain a corresponding entry, the previous period stock for the corresponding stock fields is the same as the current stock.
Fields LFMON/LFGJA of the stock tables no longer contain the current period, but one of the following periods, depending on when the upgrade took place:
Period of the last goods movement, invoice verification, price change, or other function that has resulted in period-specific information being updated
Period of the release upgrade if no such function has been performed since the system was upgraded
The current period is still recorded (as prior to Release 4.5A) in table MARV.
Planning
In a future release, it is planned for the data in the material ledger to no longer be updated by the period closing program. This will further increase the speed of the program.
[Back To Resultlist]
Regards
Raju Chitale

Update BUT000 attributes using APD

Dear All,
I need to update attributes of BUT000 directly using APD. Can anyone suggest how do i go about.
I have already created the necessary query but i am not sure What Data Taget i have to use.
Plz help.
Regards,
SS

Hi,
Please specify what is BUT000. Is it infoobject. Do you have any specific pseudo logic to update it.
You can use joins, routine etc to update it.
Regards,
Pravin

Suppressing zero rows using APD

Hello,
We are using APD to create a .csv file extract which is posted on the BW server. This file is created via APD using a query which in turn is loaded into a DSO. This data is then outputted into a .csv file. The problem is that we have a huge file, of which much of the rows contain zeros. Is there any way that the zero rows can be removed either before the datas is loaded into the DSO or during the extract from the DSO to the flat file. I cannot see any way to do this through APD functionality. Any help with this would be graetly appreciated,
many thanks,
Dave

Hi David,
Actually there is an option of appliying transformations in APD.There is a transformation type of ABAP routine which you can directlr drag and drop directly.So once getting the CSV file then apply transformations on it.I think you can try this way.This is my view.
Hope this helps
Regards
Karthik

OMJJ - Where I diferentiate "Stock quality inspection" - "Stock unrestricted use"?

Good morning, experts!
I need to know how to set up a move for the input material in quality stock, without having to use the QM or configure the material. We have the standard movement 503 that is received at the stock in quality inspection and the movement 501 that the entry into stock unrestricted use. In what field of transaction OMJJ I make this differentiation?
I appreciate your help.

Hi,
If one you use 501 the stock is sent to Quality inspection, then this could happen because you have checked the Post to Insp. stock indicator in the material master (Purchasinf view).
Post to Inspection Stock
Specifies whether the material is subject to quality inspection (without inspection lot processing) and whether a goods receipt is posted to inspection stock. The indicator is copied to purchase order items and goods receipt items as a default value.
Dependencies
You can select this indicator, if no stock-relevant inspection type has been selected in the inspection setup, and therefore no stock-relevant inspection lots can be created.
If you activate a stock-relevant inspection type, the entry in this field is deselected and can no longer be maintained. In this case, a corresponding indicator in the inspection type controls whether goods are posted to inspection stock.
When you use 501 the stock should be posted as unrestricted stock, then you can move the stock from Unrestrected to Quality Inspection stock using movement type 322 (use t-code MB1B).
With movement type 321 you can move from Quality Inspection stock to Unrestricted.
Kind Regards,
Mariano

How to configure memory snapshots used in /HMUSA?

Dear experts,
Does anybody know how to configure memory snapshots? I want to call the /HMUSA and have a look at the snapshot using the Memory Inspector. But I would like to get a itemized list of the memory used, for example for the TTAB buffer I would like to know which process or transaction has used certain amount of memory in this buffer. Thanks in advance.
PS: I am using a system for test purpose and I am the only one using this system (it's not a system used in a real company, and I have an administrator account).

Hi Sam,
Please review the following note, as it might help you!!!
Tuning Output Post Processor (OPP) to Improve Performance (Doc ID 1399454.1)
R12: How to Configure the Account Analysis Report for Large Reports (Doc ID 737311.1)
Thanks &
Best Regards,

Agewise Stock Report using FIFO out of 0IC_C03

Hello,
I have a requirement where I need to create agewise stock report using FIFO. I have the stock availability from 0ic_c03.
Can any one plese tell me how to achieve the FIFO based agewise stock. I have various age buckets like 0-30 , 30-60, 60-90 etc.
If the total stock is made up of multiple receipts and I also have few issues, how can I get the balance stock based on FIFO using the GR date.
I would appreciate your help.
Regards
Vasun

Hi,
This InfoCube allows you to evaluate stocks from ERP.
A new feature in this InfoCube is the pre-existing stock key figure Valuated Stock Quantity (0VALSTKQTY) and the associated movement key figures Receipt Quantity Valuated Stock (0RECVALSTCK) and Issue Quantity Valuated Stock (0ISSVALSTCK).
This is made possible by including the InfoObject indicator Evaluation Special Stock (0INDSPECSTK) in the InfoSource Material Stocks (as of SAP BW 3.1 Content) (2LIS_03_BX). The InfoSource used up until now, Transfer BW: Stock (2LIS_40_S278), did not recognize this InfoObject.
Note the Remarks on Filling Non-Cumulative InfoCubes.
The following Basis key figures can be restricted in the query definitions to stock categories (0STOCKCAT), such as project stock, and to stock types (0STOCKTYPE), such as quality inspection:
·        Quantity of Valuated Stock (0VALSTCKQTY)
·        Receipt Quantity Valuated Stock (0RECVALSTCK)
·        Issue Quantity Valuated Stock (0ISSVALSTCK)
In this way, for example, you can evaluate the quantity of valuated project stock (Q).
The newly-included Basis key figures are only updated through the InfoSources 2LIS_03_BX and 2LIS_03_BF.
In this way, none of these Basis key figures can be used in queries that are built up on InfoCubes which were inventory-initialized through InfoSource 2LIS_40_S278. Moreover, the queries 0IC_C03_Q0013 to 0IC_C03_Q0016 cannot be used in the combination of InfoSources 2LIS_40_S278 and 2LIS_03_BF.
Note the following procedures when filling the InfoCube 0IC_C03 for the first time with non-cumulative data from ERP:
       1.      Create non-cumulatives with the program BW: Initialization of Opening Non-Cumulatives in Transfer Structure (RMCBINIT_BW).
       2.      Initialize the movements/revaluations with the program RMCBNEUB/RMCBNERP.
       3.      Post in the InfoCube using the update method Creation of Non-Cumulatives from the InfoSource 2LIS_03_BX.
       4.      Post in the InfoCube using the update method Initialization of the Delta Process from the InfoSources 2LIS_03_BF and 2LIS_03_UM.
Refer to SAP Note 0643687 (Compression of Non-Cumulative InfoCubes) regarding the subsequent steps for compression.
       5.      Compression of the request from 2LIS_03_BX with update of the marker.
       6.      Because in this case you are posting movements and revaluations in the InfoCube that occurred before the non-cumulative creation and which lead to this non-cumulative creation, you must execute a compression without updating the marker. For more information, see InfoCubes.
       7.      Thereafter, you can transfer new movements and revaluations to the BW system as usual (for performance reasons, we recommend that you regularly compress with updates of the marker, see also InfoCube Compression).
Update Logic
When updating the DataSources 2LIS_03_BX, 2LIS_03_UM and 2LIS_03_BX, the System applies the following logic:
Characteristic Value Calculation
In principle, values are updated with Plant, Material, and Stock Category only. Quantities are updated with these characteristics, as well as with Storage Location, Batch Number, and Stock Characteristic (see also SAP Note 589024: Evaluations in BW with the Characteristics Storage Location and Stck Char.).
Key Figure Value Calculation
The source field for quantities is the field CPQUABU, and for values it is the field CPPVLC.
In the update, the InfoSource fields Stock Characteristic and Stock Category control whether "special stock" key figures are updated, such as Quality Stock or Stock in Transit (only relevant for 2LIS_03_BF and 2LIS_03_UM).
The general key figures (for example, Total Stock), however, can also be restricted in queries to Stock Characteristic and Stock Category, and then deliver the same result (key word: account model versus key figure model).
The values for Stock Characteristic and Stock Category are dealt with on the extractor side in the LMCB1F20 include (routine STA_VERAENDERUNG).
The InfoObject 0INDSPECSTK (field KZBWS) also controls whether the sales order stock / project stock is valuated or non-valuated.
The system valuates the transaction key to decide whether the issue movement key figure or receipt movement key figure is updated. For more information, see SAP Note 492828: Determining the transaction key for 2LIS_03_BF + 2LIS_03_UM.
InfoSources
This InfoCube is based on the following InfoSources:
·        2LIS_03_BX
·        2LIS_03_BF
·        2LIS_03_UM
Characteristics
InfoObject
Description
0MATERIAL
Material
0PLANT
Plant
0STOR_LOC
Storage Location
0BATCH
Batch Number
0STOCKTYPE
Stock Type
0STOCKCAT
Stock Categories
0GN_VENDOR
Vendor
Time Characteristics
InfoObject
Description
0CALDAY
Calendar Day
0CALMONTH
Calendar Year/Month
0CALWEEK
Calendar Year/Week
0CALYEAR
Calendar Year
Key Figures
InfoObject
Description
0RECVS_VAL
Value Received - Valuated Stock
0VALSTCKVAL
Value - Valuated Stock
0ISSVS_VAL
Value Issued - Valuated Stock
0ISSBLOSTCK
Issue Quantity - Blocked Stock
0ISSCNSSTCK
Issue Quantity - Consignment Stock
0ISSQMSTCK
Issue Quantity - Inspection Stock
0ISSTRANSST
Issue Quantity - Stock in Transit
0RECBLOSTCK
Receipt Quantity - Blocked Stock
0RECCNSSTCK
Receipt Quantity - Consignment Stock
0RECQMSTCK
Receipt Quantity - Inspection Stock
0RECTRANSST
Receipt Quantity - Stock in Transit
0QMSTOCK
Inspection Stock
0BLOCKEDSTK
Blocked Stock
0CNSSTCKQTY
Quantity - Consignment Stock
0TRANSSTOCK
Stock in Transit
0ISSSCRP
Issue Quantity - Scrap
0ISSVALSCRP
Issue Value - Scrap
0RECTOTSTCK
Receipt Quantity - Total Stock
0ISSTOTSTCK
Issue Quantity - Total Stock
0TOTALSTCK
Quantity - Total Stock
0ISSVALSTCK
Issue Quantity - Valuated Stock
0RECVALSTCK
Receipt Quantity - Valuated Stock
0VALSTCKQTY
Quantity - Valuated Stock
0VENCONCON
Consumption Value - Vendor Consignment Stock
Units
InfoObject
Description
0LOC_CURRCY
Local Currency
0BASE_UOM
Base Un
Regards,
Hareesh

Handling Pallets w/RTP, Intercompany Stock Transfers Using STO

Hi Experts,
We are doing intercompnay stock transfers using STO with delivery & billing i.e. DC to franchisee stores. What could be the best way to handle the pallets in this scenario? I'm thinking to use RTP. Does anybody has experience with this scenario?
Any help is appreciated.
Tahnks,
KHAN

nobody replied so closed.

How to transpose the data records (rows) to column(lists) using apd

Hi,
how to transpose the data records (rows) to column (lists) using apd in sap bw.
I do not want to use abap routine.only use the transpose rows to list transformation .
Pls provide the step by step procedure .
thanks,
Nimai

Save youe file to transpose as a csv and in the header row of your file for the columns you want to transpose you need to put some soer of a tag before the column name (ie your colum header was for a period budget will be something lie 2011001:ZFIBDD)
1. You will need to create a new apd process (rsanwb)
2. Insert a "Read from Data File" data source object and map it file (,csv)
3. insert a transpose object into your apd process (middle row 4th one over in the transformations section)
4. under the definition tab in the transformation object select all the columns that are to be transposed into rows and move them to the transformed area, the grouping fields section should contain the rows that you want to now be columns
5.under the transformation tab enter in the seperator you selected under the Field Name/Infoobject area (ie. ZFIBDD)
6. under the details tab you need to enter in all the fields to be transformed and tner the transposition field (ie ZFIBDD)
7. Then you can insert a set of transformations and a DSO and link the newly transposed fields into that.
hope that helps

Any reference company listed on US Stock Exchange using SAP B1

Did anyone knows of any company listed in US Stock Exchange using SAP Business One?
Thank you in advance.

Hi Crypton,
Please close this thread, else it seems like i wasted my time.
I did speak to a high level SAP executive today, I got two names for you - the company in American Stock exchange that have SAP Business ONE. But it is qualified usage, the companies are so big, they can not just run on SAP B1, however, they do use SAP B1 in some subsidiary or division.
We can not expect SAP B1 a less than 50K solution to replace a 500K solution. That is just not going to happen. SAP B1 is for small to medium business however, can serve as part of certain division in a larger 100 or 500 fortune companies.
The two take away names are - For manufacturing it is Callaway Golf ELY
In Canada and some parts of USA there is a major Canadian Coffee/Donut/FastFood chain called Tim Horton - It is traded in US exchange under the symbol THI
Last one for you is Disney - DIS.
You are welcome!

Loading complex report data into a direct update DSO using APD

Dear All,
Recently, I had a requirement to download the report data into a direct update DSO using an APD. I was able to perform this easily when the report was simple i.e it has few rows and columns. But I faced problems If the report is a complex one. Summing up, I would like to know how to handle the scenarios in each of the following cases:
1.   How should I decide the key fields and data fields of the direct update DSO ? Is it that the elements in ROWS will go to the
      key fields of DSO and the remaining to the data fields? Correct me.
2.   What if the report contains the Restricted KFs and Calculated KFs? Do I have to create separate infoobjects in the BI
      system and then include these in the DSO data fields to accommodate the extracted data ?
3.   How do I handle the Free Characteristics and Filters ?
4. Moreover, I observed that if the report contains selection screen variables, then I need to create variants in the report and
     use that variant in the APD. So, if I have 10 sets of users executing the same report with different selection conditions, then
     shall I need to create 10 different variants and pass those into 10 different APDs, all created for the same report ?
I would appreciate if someone can answer my questions clearly.
Regards,
D. Srinivas Rao

Hi ,
PFB the answers.
1. How should I decide the key fields and data fields of the direct update DSO ? Is it that the elements in ROWS will go to the
key fields of DSO and the remaining to the data fields? Correct me.
--- Yes , you can use the elements in the ROWS in the Key fields, but in case you get two records with same value in the ROWS element the data load will fail. So you basically need to have one value that would be different for each record.
2. What if the report contains the Restricted KFs and Calculated KFs? Do I have to create separate infoobjects in the BI
system and then include these in the DSO data fields to accommodate the extracted data ?
Yes you would need to create new Infoobjects for the CKF's and RKF's in the Report and include them in your DSO.
3. How do I handle the Free Characteristics and Filters ?
The default filters work in the same way as when you yourself execute the reoprt. But you cannot use the Free characterisitics in the APD. only the ROWS and cloumns element which are in default layout can be used.
4. Moreover, I observed that if the report contains selection screen variables, then I need to create variants in the report and
use that variant in the APD. So, if I have 10 sets of users executing the same report with different selection conditions, then
shall I need to create 10 different variants and pass those into 10 different APDs, all created for the same report ?
--- Yes you would need to create 10 different APD's. Its very simple to create, you can copy an APD. but it would be for sure a maintance issue. you would have to maintain 10 APD's.
Please revert in case of any further queries.

Project Stock report using QBEW and QBEWH tables

Dear All,
First of all Happy New Year to all of you.
Here is my question: I want to build a ABAP report for stock situation for project stock. The report demands the stock by closing month. Suppose I run the report for month 11/2010, it should show the closing stock at the end of the month 11/2010.
Now I am using the values from table QBEW for this purpose.But QBEW table shows only current entries. If a material stock is changed or value is changed, it goes into history table QBEWH.
Now problem is that if I try to make sum of QBEW and QBEWH, the stock value is excessive. Now I am not sure which entries I should consider from QBEWH table for this purpose.
Has anybody worked on similar requirement?
Thanks in advance!
Regards,
Mahendra Dighe

Hi,
Please try the report S_P00_07000140 - Inventory and Raw material for special stock report.
Thanks.
abdul

Is there a way to create consignment stock without using a Purchase Order

Hi Gurus,
Is there a way tp created unrestricted consignment stock for a material without first creating a Purchase Order and then using MIGO. Is there a way to create directly into inventory?
Thanks for your help!

Hi Charlie/All,
Still having the same issue.
I checked t-code OMEV to make sure Consignment Info Record is activated
I checked the EINE table to verify the Infor Record was created for consignment
In MIGO I use the following:
Goods receipt - other - movement type 501K
material, vendor, qty entered
error msg: purchase info record not founf in purchasing organization??
not sure why..thank for all your help so far...

Use APD to fetch data from Query's Structure

Hi,
i have created a query , with a fixed structure in the Row area and two keyfigures.
I have this query on DSO.
i want to store the same query output to one table.
How can i achive this?
I think to use the APD, but as i have fix structure in query , APD is not the solution . correct me if i am worng.
Please suggest.
Regards,
Macwan James.

Hi SVU123,
Currently I am trying to load data into ODS only. But I want to avoid this path. I can always extract data out of the ODS to Flat File through Open Hub, but that will require twice the time to extract data.
First from Query to ODS and second from ODS to Flat File through open hub.
Basically, I want to automate this process and that is why I don't want to opt the path for RSCRM_BAPI t-code.
- Danny

Initial entry of stock (561) using MB1C

Hi all
Can someone help me understand how to create initial entry of stock using references.
I see there are options to create "To purchase order", "To Reservation", etc. Do they mean that we can create initial entry with reference to purchase order?
Also there is option to create with reference to Material document. What kind of Material documents can be used as reference?
Thanks in advance
Regards
Mui

Hi,
All this options are for other goods receipts means without reference to purchase order.
otions are To Reservation, To Order.This order means not Purchase order i.e Production Order or Internal Order.
Initial entry are used to Upload the stock at initial stage i.e at the time of Cutover strategy,we uploading the initial stock which is present at plant at SAP system and after that only we process the normal transaction like PO, MIGO..
Regards
Sanjay L

Stock Snapshot using APD

Similar Messages

Maybe you are looking for