Where to see Forecast in ECC released from APO DP

Hi Experts,
we are releasing forecast data from APO DP to ECC.
can anyone please let me know in ECC is there any table and transaction where we can check the released forecast from APO.
Other than MD63.
Thanks in advance.
Regards
Maddy

Hi,
You can check it in MD63 - Display Planned Independent Requirements
Or Menu path:
SAP Menu->Logistics->Production->Production Planning->Demand Management->Planned Independent Requirements->Display
Regards,

Similar Messages

HT1657 Where to see the movie I rent from AppleTV

I rent this movie from Apple TV movies section. I clicked rent and watch now, but it said "I have already rented this item but it has not been downloaded. To download it, go to the Settings menu, select Downloads, then Check for Downloads." First, there is no Setting memu under Movies, I went to the main memu Settings, there is no Download memu. So, I checked iTunes Store, Check For Rentals, it's loading forever, no result either. I just want to know where can find the movie I rent??????

Hi SlowZhu,
I had the same problem and found the solution from this thread:
https://discussions.apple.com/message/23197787#23197787
if you log out of your apple itunes accound and then log back in again it should work - it should appear in a separate 'Rentals' section of the movies page.

Releasing fcsts from APO DP with time of 12:00:00

I am using APO V5.1
I know by default that forecasts are released from APO DP at the start of the buckets, ie 00:00:00.
How can I ensure that that the forecasts instead have a time stamp of 12:00:00?
Thanks for any advice on this...

I am using APO V5.1
I know by default that forecasts are released from APO DP at the start of the buckets, ie 00:00:00.
How can I ensure that that the forecasts instead have a time stamp of 12:00:00?
Thanks for any advice on this...

Transferring Product Master Data Changes From APO to ECC/R/3

Is it possible to transfer product master data changes in APO to ECC via the CIF? If so, does it require custom coding?

Hi James,
In all the different clients where APO is being used with ECC systems. ECC system is always the main system (system of record) which contains all the master data and data present in ECC supposed to be the reference for APO system for planning purpose.
Generally it is not recommended to transfer master data from APO to ECC but as mentioned earlier by some experts you may have ways to do that.
I would be interested in the business scenario where one needs to transfer master data from APO to ECC.
Thanks,
Anupam
Edited by: Anupam Sengar on Aug 11, 2011 12:31 AM

How to configure for the give senario where we from APO demand planning, we provide baseline forecast into TPM

Hello Guru's,
Request for information on smart documentation on the integration between Trade Promotion Management and SCM-Demand Planning from an architecture perspective how to configure for the give senario where we from APO demand planning, we provide baseline forecast into TPM and from TPM promotions values can be considered in to APO demand planning: can anybody give me some insight on it.
Thanks in advance.
Kumar

Hi Praveen
There are several ways you can connect a DP system to a TPM. How are your interfaces and systems setup?
Option1:
Extract the baseline from APO to a BW cube, extract the data out of BW, may be using infospokes/open hub and pass it on to TPM.
2. Have a custom program written in APO-DP to extract the selected keyfigure data at the aggregation level into an interface or a .txt file into APO directory and use some data transfer service such as EDI to take this data and send to TPM.
In my experience it is simple to define an integration process. The much larger and complicated aspects are the date adjustments and the aggregation levels.
Date adjustments:
Understand the basis of the data in APO and TPM. APO is usually at the requested delivery date or material availability date ( when the customer like a store wants the product). However TPMs are usually at the consumption date ( when an end customer like you and me but from store shelf). Depending on the product and business style this can mean several days difference. Let's say it is 25 days on average, you need to add 25 days to APO base line date to get the TPM consumption date.
Aggregation level:
This can be product or customer. If the planning in DP is at product sku level and the TPM is at packs or brand level, you need to aggregate the data up before loading to TPM. The same with customer.
To me the most complex part of the integration is to understand and transform the data in a meaningful way and a strategy to sustain this integration by keeping both DP and TPM in sync in terms of master data. Also important to have a process for identifying exceptions and failures. you send baseline from DP to TPM and if it fails, how do you know? how do you trouble shoot?
Hope these help.

How to keep past forecasts in R/3 after release from DP

Dear experts
We release forecasts from a demand planning book, data view in monthly buckets starting in current month. (now July 2011)
When the release is done, the forecasts before current month (M-1, M-2) are automatically deleted in R/3. It seems each release overwrites PIRs in the past in MD04. (also no longer visible in MD63, MD73)
How can we keep the unconsummed forecasts of the previous month when we release on current month?
Thank you
Elynn
Edited by: ELynn640 on Jul 20, 2011 11:20 AM
Edited by: ELynn640 on Jul 20, 2011 11:21 AM

Hello,
Please notice the following points when release forecast from APO to R/3:
1)The existed PIRs at R/3 side will first be cleared out, both past and future.
2)No zero forecast will be released.
To acheive your requirement, you can do the following:
1)Apply notes 446688 and 812133 to avoid clearing out the existed forecast in R/3.
2)Implement BADI /SAPAPO/SDP_RELDATA method CHANGE_RELDATA to add zero forecast values in the future.
This is used to clear the existed forecast at R/3 side in the future.
Best Regards,
Ada

Where to see generated SQL statement from jdbc adapter?

Hi everybody,
where can I see the generated SQL statement from JDBC adapter?
Regards Mario

Yes and True lterally means the same, but alas XI does not understand literature..
Just checked the note as well, as you are correct!
Regards
Bhavesh

To see in a ECC report the PO's created against a MM contract

Hello,
Someone know how I can see in a ECC report the PO's created against a MM contract.
Cheers,
Marta

Hello,
extract records from table EKPO where field "Purchase Requisition" (EKPO-BANKF) is blank. Otherwise you can run transaction ME2N, follow the menu path "Edit --> Dynamic Selecyions", and choose the filed "Purchase Requisition" among "Purchasing Document Item" folder, then the field will show up and you can use as selection criteria "Purchase Requisition" = blank.
Hope to be useful.
Best regards,
Andrea

HTTP adapter: where to see the transformed output message

All,
I am a beginner in Webservices/HTTP interfaces in PI. I have to make changes on an existing custom interface which uses HTTP adapter. I have done the changes in the message mapping and tested it using the test tool. It seems OK.
However when we do end-to-end testing, data is flowing but bussiness needs a copy of the transformed data that has been sent out from PI.
I checked RWB->Message Monitoring-> Integration server(Database) and it showed the successful message. When I drilled further into this message, it showed the SOAP message (Version 0 and Version 1 with payload). The payload showed the data that ECC had sent to PI and not the transformed data that went out from PI to 3rd party via HTTP adapter.
Appreciate if you could guide me in right direction regarding where to see the Output/Transformed data that is actually sent to third parties.
I have checked SXI_MONITOR as well in PI but that also shows the payload only and not the transformed data.
Regards
SK
Edited by: Shirin K on Feb 18, 2010 3:10 PM

Hi ,
Go to particular message in SXI_MONITOR. In Message there will be window on left hand side. There will be Technical Routing.
Technical Routing> Payloads->Maindocument. This shows the Output data.
If you are not able to see Technical Routing inform you basis team they need to do some configuration in SXMB_ADM
Edited by: Rajhans Abhay on Feb 18, 2010 4:29 PM

Where to see query details(urgent)

Hi xperts,
Can you please tell me where to see the runtime detaile of the query if we excute in the browser or in query analiser it is not aback ground job by default.Due points will be given.
Thanks in advance,
Dan

Hello Dan,
I am not sure about the BW release you are using, therefore, I would provide the solution for both the releases.
BW 3.5 (NW04)
In case, you are using BEx Analyzer or the browser for executing the query, you can see the query runtime statistics in the BW system only if the BW statistics for the InfoCube are activated on which the query is running.
Therefore, please activate the BW statistics on all the Basic InfoCubes on which the query is running. You can do this from TCode: RSDDSTAT or from RSA1-> Tools -> BW Statistics for InfoProviders.
Now, execute the query from BEx or the portal and after executing login to the BW system (ABAP system) and go to Transaction SE16.
In transaction SE16, enter the table name as (Table Name = RSDDSTAT)and in the QueryID field enter the technical name of the "query" and then press execute.
Now, you will see all the runtime statistics for the query, like the total runtime, DB time, OLAP time and the frontend time.
The other way to see the query details is to run the same query in the "Query Monitor" (TCode : RSRT) with the option "execute and debug" and in the options select "display runtime statistics". After you execute the query on the output screen, just go back and you will see the query statistics for the current exection of the query.
BI 7.0 (NW 7.0)
Same things need to be followed here also.
The difference is that you can activate the BI statistics on a query also in case of BI 7.0.
Therefore, from "RSA1 -> Tools -> Settings for BI statistics" or from TCode: RSDDSTAT, activate the statistics on the query, you are referring to.
Now, after running the query in BEx Web Analyzer or BEx Excel addin, you can again go to SE16 and here now, you need to enter the table name as "RSDDSTAT_OLAP" to see the new BI query runtime statistics.
For getting the details of the DM time, you can also use the RSDDSTAT_DM table.
The other option of RSRT is also valid in this case.
I hope, I have answered your query.
Please let me know in case of any doubts.
Regards,
Yash Vardhan

Where did Display Duplicates go in release 11

Where did Display Duplicates go in release 11? Can't find where they put this.

Two Windows scripts to make playlists of Duplicates and Exact Duplicates. Use shift-delete to remove selected tracks from the library as well as the playlist.
There is also my DeDuper script if you don't want to do it by hand. Please take note of the warning to backup your library before deduping. See this thread for background.
tt2

DP Forecast into ECC

Hi all,
Pl let me know what's the best way to bring DP forecast into ECC. Should I publish it from SNP, or transfer from DP. I look for similar result in MD04 and Product View.
Thanks
Vardev

Hi
Yes with /SAPAPO/MC8U - Maintain Transfer Profiles you can create the Transfer profile which will be used to release the FCST in ECC system as planned ind. Requirement . Detail information is below for your reference.
http://help.sap.com/saphelp_scm41/helpdata//EN/c9/b4df8b70c011d398450000e8a49608/frameset.htm
If you are using respective strategy 40 i.e. planning with final assembly it will consume the FCST by sales order. The unconsumed FCST will still be present in MD04 as planned ind. Requirement.
So at the end , you will have 2 demand element sales order and unconsumed FCST as form of planned ind. Requirement.
Thanks
Amol

Unable to transfer Forecast to ECC

Hi Experts,
We are unable to transfer foreact from APO Dp to ECC.
we can see the forecast data in Planning Book and transffered to ECC through Batch Job. When we check in spool. It is showing message "Transffered data to R/3. But we can't see the forecast in MD63.
Thanks & Regards,
Manasa

1) Check if Product location exists in ECC and APO.
A) Both are same
2) Check transaction MD73 instead of MD63. If forecasts are already consumed, you will not see them in MD63.
A) When i check for Plant X, I can able to see forecast data in MD63.But for Plant Y in MD63, it shows message "No requirements were found which correspond to the selection criteria".
As you asked me to check data in MD73, it shows message "No requirements were found which correspond to the selection criteria".
3)In the activity definition in APO if you do not specify a Requirements Type, check what Strategy Group is assigned to the Material master in ECC. Then go to customizing and identify the Planning Strategy. Check if the Planning Strategy has a value assigned for the Requirements Type for Independent Requirements.
A) Y plant is just a replica of Plant X. Both are having same parameters in Material master (ECC)and in Product master (APO).

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

How to have multiple images on the same screen? like in the movies where you see several actions at

how to have multiple images on the same screen? like in the movies where you see several actions at the same time ....
i don't find a tutorial in adobe tv....
thanks !!

The short answer is that you'll put the source clip(s) for each inset on a different video track, all stacked up. Then use the Scale and Position effects (under "Motion" on the Effect Controls panel) to reduce their size and place them where you want.
If the content of an inset will involve edited content (where you're cutting among various clips or just trimming out unwanted content from a single clip), then you'll probably find it easier to do all those edits in one sequence, then nest that sequence in the master sequence, where you apply the Scale and Positioning effects. That will save the step of applying the scale and position effects to each edited track item.

Where to see Forecast in ECC released from APO DP

Similar Messages

Maybe you are looking for