cancel
Showing results for 
Search instead for 
Did you mean: 

0IC_C03 Compression n Marker update..

Former Member
0 Kudos

Hello all,

I'm working with SAP Net Weaver 7.02 and BI Content 7.06. While using Standard Cube: 0IC_C03 Material Moments which has three DataSources

i) 2LIS_03_BX

ii) 2LIS_03_BF

iii) 2LIS_03_UM

I have completed stet-up table with company code for above there datasources:

Now, I need to load data into infocube. Following are the steps/sequence which I',m following, Could you please have a look, Am i on the right track?


1: 2LIS_03_BX will be loaded first and only one time with the update mode being "stock initialization" in both infopackage and DTP.

    First, it would be compress and then marker update? No delta for would be run.

2: 2LIS_03_BF & 2LIS_03_UM these data sources need to first ''Initialization without Data''...then.

  Full Load....  No need to be Compressed using marker update.

    and afterwords, I shall run Delta with Compress with Marker Update


3: How and from where i need to compress and marker update? Do I need to Install Info package from BI content?

4: I have been reading SCN posts, DTP that datasource 2LIS_03_BX need to be Install from BI Content, if so then

    what is the Technical name of DTP?

5: DTP for datasource 2LIS_03_BX  can I create own my to use it?

6: For datasources 2LIS_03_BF & 2LIS_03_UM , How do i manage its Delta Management?

    Do i have to compress and marker update every time during delta upload/request?

7:  Do i have do first compression and then marker update? From where I can use compression?

Regards

Arshiyan

Accepted Solutions (0)

Answers (9)

Answers (9)

Former Member
0 Kudos

Hello All

Around 1 hour ago, I have posted a post regarding my entries were not showing in LBWQ outbound Queue and I tried to change update mod but  from Unseriallized V3 to Delta Queue.

but I have got error which I started above my post.Afterwords, i didn't do any thing with it and leave as it is.

Around, 20 minutes Ago, I refreshed Outboutund Monitor (LBQW) and saw entries for datasources

2LIS_03_BF & 2LIS_03_UM   which dispersed from there.  Then I went on RSA7 where there I saw those data sources with its entries as you see below screen short!

1) What has happened, please elaborate it?

2) How entries has been moved out from LBQW to RSA7 without doing any thing?

3)  On LBWG, Application 03, Its update mode is still ''Unserialized V3, why so?  as you see in the screen short below!

4) Next, do I have to run Infopackage on Infocube for delta?

Thanks

Arshiyan

former_member209895
Contributor
0 Kudos

Hi Arshiyan,

     Firstly Unserialized V3 and Delta queue are not two update modes. Unserialized V3 is an update mode but Delta queue is a queue to collect the delta LUWs for all the different types of update modes. Inventory Controlling application is already set to Unserialized V3 update in your system.

1) What has happened, please elaborate it?

Answer: There was initially no data in LBWQ for 03 hence the LBWQ did not display the queues related to 2LIS_03_BF and 2LIS_03_UM, within some time the postings happened and there were some LUWs related to 03 queue, hence the queues appeared in LBWQ.

2) How entries has been moved out from LBQW to RSA7 without doing any thing?

Answer: A V3 job has already been scheduled in the background, which runs at a certain frequency like once a day, hourly etc based on the start conditions input when the job was created, hence this V3 job has carried all the LUWs from LBWQ to RSA7.

3)  On LBWG, Application 03, Its update mode is still ''Unserialized V3, why so?  as you see in the screen short below!

Answer: It has already been selected for Unserialized V3 update, so it will only use V3 jobs to pull the data from extractor queue and move it to delta queue. And remember Delta queue and Unserialized V3 are not update modes.

4) Next, do I have to run Infopackage on Infocube for delta?

Answer: Yes, you have to run infopacakges with update type being DELTA to pull the data from the delta queue - RSA7 and move it to BW.

Please go through documents related to extraction - LO Extraction to understand the entire flow, only then will you be clear headed. The questions here will get answers, but they will never help you connect the dots unless you have the idea of extraction.

Regards,

  Manohar. D

Former Member
0 Kudos

Hello Scn Experts

                      Thanks for such help n time to all especially Mr. Manohar.

I'm working on Production system where entries are being input on daily bases.

I have tried to choosed option ''DELTA QUEUE'' but i got the following error message!

Change of update mode not possible due to open V3 update -> Long text

Message no. MCEX160

Diagnosis

You are not allowed to change the update mode for application 03 from V3 to another method. This is because there are still V3 update entries for update module MCEX_UPDATE_03 that have not been processed yet.

1) What is this message all about and how to resolve this issue, please elaborate it?

2) I have already loaded full data on Friday (4 June 2013). Now, If i do  Unserialized V3 to

    Delta Queue, can it possible i loose entries during posting?

3) Do I have to do this job while posting is block?

Thanks

Arshiyan

former_member182343
Active Contributor
0 Kudos

Hi Arshiyan,

Above Error means :

- You have already productionised Inventory (03) application with unserialised V3 update and postings are beeing updated through Update table (SM13 ) to RSA7.

Here you can't change delta mode in prod.

If you want to change you have to do at DEV and transport to prd.

Precautions to do:

1. Clear SMQ1/RSA7

2. Requied down time.

WR,

Vijay

former_member209895
Contributor
0 Kudos

Hi Arshiyan,

        The error message just states that a V3 update is already setup, which means that the JOB control settings are taken care of. I'm afraid that you might have just stopped the V3 schedule in the process of checking. As I've seen the Job control screen is extremely shy, any small changes and the start parameters go to RED. Please check if its running again.

Also LBWQ will only display the queue and data if Queued extraction is chosen, if an Unserialized extraction is chosen then you will have to check for update queues in SM13.

2) I have already loaded full data on Friday (4 June 2013). Now, If i do  Unserialized V3 to

3) Do I have to do this job while posting is block

    Delta Queue, can it possible i loose entries during posting?

Answer: If V3 jobs are already running, then it doesn't matter, they would've collected and conveyed the records to delta queue, if not then yes you will have to load all the missing records through Full Repair. JOB control should be taken care of as soon as the statistical update from setup tables is completed and initialization is run.

A humble request: Please do not club multiple questions into one thread. If any person is searching web regarding compression and marker update, and stumbles upon this thread, the person would've to unnecessarily go through the extraction part.

Hope this helps,

Regards,

  Manohar. D

Former Member
0 Kudos

Hello All,

Thanks for being kind and helpful.

I have successfully loaded data into my standard infocube on Friday afternoon.

1) For Datasources 2LIS_03_BF   and  2LIS_03_UM

    I have I chosed the upload mode "Initializing the delta process'' WOT and then Full respectively

     and then marker update with compression.

     In Delta Queue maintenance we can see above two data sources as in screen short!

  Today, I have used T code: LBWQ (qRFC Monitor) Outbound Queue to look data entries for above two datasources, but I have found no entry there, as you see in the screen short...

For delta entries, Do I have to run info package for Delta only or data entries would get in

in outbound delta queue?

Thanks

Arshiyan

former_member209895
Contributor
0 Kudos

Hi Arshiyan,

       Infopackage has no role in enabling the documents to fill up the extractor queue [LBWQ].

Please go to LBWE and choose the job control for inventory controlling and select the Queued Extraction. This will enable the posting of LUWs to the extractor queue LBWQ. Now to get these LUWs to the delta queue, you will have to schedule a V3 job - again from the JOB CONTROL option in LBWE for inventory. This will make sure that the collected LUWs are posted to Delta queue. If now a delta infopackage is triggered the data will move up to BW from delta queue.

Hope this helps,

Regards,

  Manohar. D

former_member182343
Active Contributor
0 Kudos

Hi,

If your question is why LBWQ has records and RSA7 doesnt have ..

LBWQ holds transactions related to datasource which are Queud delta enabled.

Run V3 job / job control by going to LBWE or run rmbwv303 programme using SE38 T code.

Now you will find records in RSA7. Then trigger Infopackage to get data into BW.

Regards,

Vijay

Former Member
0 Kudos

Hello SCN experts

Thanks for all but i especially deeply big kindly thanks to Mr. Manhor and Mr. Andand


Regarding update mod, i'm bit confuse regarding these tow data sources

2LIS_03_BF & 2LIS_03_UM

1) How many and which UPDATE MOD, i need to select?

i) 2LIS_03_BF  for this data source

  1st, i shall click on    ''Initializing the delta process''     then which update mod to select and how 

   many  in total respectively?

ii) Same above question goes with this    2LIS_03_UM   which update Update Mod respectively and which are?

2) Do i need to install any Info package DTP for above data sources , if so please let me know the technical names

Regards

Arshiyan

former_member209895
Contributor
0 Kudos

Hi Arshiyan,

     You are welcome, I just shared what I had worked on, didn't go out of my way to find answers, but feels good to know it helped.

The datasources 2LIS_03_BF and 2LIS_03_UM are the same as rest of the LO datasources, they have a delta queue, their setup tables are filled just like other LO datasources. And the update mode you will be choosing would be DELTA.

1) How many and which UPDATE MOD, i need to select?      

i) 2LIS_03_BF  for this data source

  1st, i shall click on    ''Initializing the delta process''     then which update mod to select and how  many  in total respectively?

Answer: To enable Delta process first you initialize it by running the infopackage on Initialize Delta process with / without data transfer. This is done post setup table filling. So first fill the setup tables and then initialize with data transfer for your case as its a fresh implementation.

steps to follow:

1. Fill setup table in R/3 for the particular datasource.

2. Run the infopackage with update mode being - Initialize the delta process with data transfer.

3. Upon successfull completion of initialization, set up the V3 job run in R/3 using Job control in LBWE.

4. Schedule the load of delta infopackages hereafter.

Only deltas will run from now on, unless you need to correct the data through selective deletion and reload.

ii) Same above question goes with this    2LIS_03_UM   which update Update Mod respectively and which are?

Same above answer holds good for 2LIS_03_UM


2) Do i need to install any Info package DTP for above data sources , if so please let me know the technical names

Answer: You may search and install or you may create an infopackage and DTP for yourself. It hardly matters hereafter.

Please go through the below three documents which will help you with Inventory, the last one would be helpful to you as you are struggling with the data loading part:

Overview of IC_C03 flow:
http://scn.sap.com/docs/DOC-11289

Installation of datasources:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0783925-f4be-2c10-9c89-ffa108f72...  

Movement type overview:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e00860a4-350f-2d10-29a0-fc09681a8...

Data Loading:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/906b837a-0d54-2c10-08b8-bde703375...

Hope this helps,

Regards,

  Manohar. D

Former Member
0 Kudos

Hello all 

For datasource 2LIS_03_BX, infocube 0IC_C03, I successfully loaded data records which are 16304 into PSA and then executed DTP. Afterwords, i did Compression and No Marker Update.

On Collapse tab,  I have clicked on Released button. Then,I clicked on Request tab.........and looked up Compression status  which is '' request for compression is scheduled'' I kept refreshing many times but nothing happen.

please see in the below screen!

Then I clicked on Collapse tab again and clicked on log button, again nothing happened.

On remaining the same tab'' Collapse'' i have clicked on ''Display External Batch Job'' and executed it and got the below screen, as you see in the screen short below.  Its delay time is also increasing and the job status is not showing any thing/empty.

1) Could you please let me know wot's going on?

2) Data records are not in big amount, then why job is not being completed/finished?

Regards

Arshiyan

Former Member
0 Kudos

Hi,

Before Going in collapse Tab, go to rollup tab , include request is in request id option , then go to collapse tab & do , whatever you are doing.

Regards,

Anand Mehrotra.

former_member209895
Contributor
0 Kudos

Hi Arshiyan,

   If you look at the job status, it says "RELEASED", which means that the Collapse job has not started yet but is in released state. Did you start the job with the selection being IMMEDIATE ? If not the job is not likely to start immediately.  Double click on the job and look at the schedule timing. Also check in SM37 if many jobs are having a delay seconds and going into RELEASED state inspite of being triggered immediately or on schedule. If such is the case then it is a resource issue, please do not burden the system any more by triggering any jobs till the delay time gets down. Get in touch with Basis to help you in killing the non important jobs and hence making the resource available.

Hope this helps,

Regards,

  Manohar. D

former_member209895
Contributor
0 Kudos

And Roll up only if you have aggregates, I'm sure that you would not have aggregates created at this stage. So please check on the job scheduling and the application server availability.

Regards,

  Manohar.. D

Former Member
0 Kudos

Hi Arshiyan,

No need to install Info package and DTP from Business content.You can create the IP and DTP on your

own  to load data. Regarding compression, successive deltas must always be compressed to avoid

performance issues. To know marker update and compression in clear,check the link

http://wiki.sdn.sap.com/wiki/display/BI/Inventory+Management+-+Marker+Update,+No+Marker+Update+(BW-B...

-Padmaja

former_member209895
Contributor
0 Kudos

Hi Padmaja and Arshiyan,

     It would be better if you install the DTP -  DTP_DD6NO31LIYURWPK37I2QL59I0 for datasource 2LIS_03_BX, coz only this DTP has the extraction mode as 'Initial Non-Cumulative for Non-Cumulative values'

And let the infopackage be 0PAK_D4CPWC4DFZG2ZG6CLD5FVN9SO (2LIS_03_BX_STOCKINIT_R3) which has the update mode as "Generate Initial Status".

Hope this helps,

  

Regards,

  Manohar. D

Former Member
0 Kudos

Hi Arshiyan,

Please go through this,

http://scn.sap.com/docs/DOC-41821

Thanks,

Ram

Former Member
0 Kudos
RamanKorrapati
Active Contributor
0 Kudos

Hi Arshiyan,

please search in scn, you will get lot of threads related to this. read them  and follow the required steps. while implementing steps if you face any error please share it.

Please check this content.

http://scn.sap.com/people/pascalgabino/content?start=40

Thanks

Former Member
0 Kudos

HI,

Please go through 0ic_c03 steps, As you rightly said 2LIS_03_BX is one time activity with upload mode "create opening balance ".

1.  Loading the opening stock balance (InfoSource 2LIS_03_BX) into InfoCube

0IC_C03. In the InfoPackage, choose the upload mode “Create opening balance”

2. Compressing the request containing the opening stock that was just uploaded. Make

sure the "No marker update" indicator is not set.

3. Loading the historical movements into the InfoCube 0IC_C03 via the DataSource /

InfoSource 2LIS_03_BF. Choose the upload mode "Initializing the delta process"

here.

4.After successfully uploading the historical material movements, the associated

request has to be compressed. You must make sure the "No marker update"

indicator is set. This is necessary because the historical material movements are

already contained in the opening stock

5. You do not need to compress the requests directly after the upload. If you do

compress afterwards, this has no effect on the compression settings. This

means in all cases:

a) The request in which the opening stock was loaded must always be

compressed with a marker update

b) The request in which the historical material documents were contained

must always be compressed without a marker update and

c) Successive delta uploads must always be compressed with marker

updates.

Regards,

Anand Mehrotra.