633W

[Former Member]

Hi, Whilst validating some inventory reports it was noticed that materials with movement type 633 W (issue consignment billing) are reported in MC.1 with volume quantities but no value assigned. This gives an impression that the volume for physical material movements are duplicated as MC.1 will use mvt type 631 & 633 as double counting volume for the same physical material but only associate 1 value (mvt 631), which is correct but from an inventory at site level reconciliation causes us some reporting calculation issues.

We would like to request that movement type 633 W be disassociated with statistical reporting if possible.

I dint quiet undertsand the issu itself. Can somebody help out.

Thanks,

Sujatha Iyer

[former_member186100 · Accepted solution]

Go to OMJJ ,

select movt type 633 and make it not relevant to statistical reporting

I believe it will help for new transactions , try it testing environment. Updating prior data may need info structure regeneration.

warm regards

Avinash Goswami

[Former Member · Accepted solution]

Hi Avinash,

Thanx for your input. But i think by doing the above action mentioned   the non relevance of  movement type 633 will have an impact on these transactions too.  I want this changge to be only on the report to be generated. Kindly provide me with some help.

Also it will be helpful if you can explain me the issue.

Thanks,

Sujatha Iyer

[former_member186100 · Accepted solution]

Hi Sujatha,

The statistical relevance indicator is purely to control updation of LIS(Logistics information system) info  structures, it will not effect anywhere else. Every time we make a material movement , it has to be updated in LIS info structures so that it can be viewed in LIS reports. The report you previously mentioned MC.1 uses "S039 " info structure as the base. Once you make movement 633 not relevant for updation , its effect  will not be counted  in LIS reports. We generally remove transfer postings from standard analysis of reporting as it gets counted in both , GRs and GIs ( transfer posting has both lines debit and credit). Meanwhile you can try this option too

warm regards

Avinash Goswami

[Former Member · Accepted solution]

Hi Avinash,

That means by making  that movement type non relevant the above mentioned tcodes wont have any impact in their execution??
And going by your explaantion above you mean that if i make the Mtype 633 non relevant it will not be viewed in any of the reports generated right ?

But my requirement is this effect should be seen  only in a single report
Is this possible?
Or else  goin by the issue can  i proceed in the same way suugested  by you .?

Thanks,

Sujatha Iyer

[ajitkumar · Accepted solution]

material documents with this movement type, from whatever txn it is created, wont get updated in the info structure.

[former_member186100 · Accepted solution]

Hi Sujatha ,

It is just making non relevant for statistical reporting, LIS mean report with transaction "MCXX" where X is variable. The config i pointed out will not effect anything else. Plus , please test the changes in testing environment before taking it to production server. You can also try running report with option i suggested in previous post.

warm regards

Avinash Goswami

[Former Member · Accepted solution]

Hi Ajit and Avinash,

I got that it wont affect any other thing ...but i want this thing to be reflected  in only one report in MC.1

Is this possible ?

Thanks,

Sujatha Iyer

[former_member186100 · Accepted solution]

It will effect all LIS reports .

[former_member186100 · Accepted solution]

Rather then setting statistically relevant indicator to "blank" , you can change it to ' 2 ' and run report MC.1 with std. w/o distribution  radio button selected in selection screen , it will give you the results you wanted.

warm regards

Avinash Goswami

[Former Member · Accepted solution]

Hi Avinash,

What does the second option means?
By selecting that do you mean that the removal of 633 movement type will be impacted in only one report and  not on all reports ?

Thanks,

Sujatha.Iyer

[former_member186100 · Accepted solution]

Hi Sujatha,

What i am suggesting is you change statistically relevant indicator to '3"

then when you want 633 to reflect in report run  MC.1 with following option

when you dont want 633 to be reflected in report MC.1 select following option

hope this helps

warm regards

Avinash Goswami

[Former Member · Accepted solution]

Hi,

But whatever  option i select the changes  will be reflect in all reports ? r

[former_member186100 · Accepted solution]

in MC.1 series only

it will not effect MM reports

[Former Member · Accepted solution]

The requirements of user is dat the only the movement type 633 should not be reflected and 631 should be reflected in the reports .

So wanna ensure that by doing the above options will only 633 movement type will be removed and will the effect of 631 movement type remain ?

Thanks,

Sujatha Iyer

[former_member186100 · Accepted solution]

only 633 will be removed.

[Former Member · Accepted solution]

Avinash,

Should i put option 2 or option 3 in the statistically relevant field in omjj transaction ??

[former_member186100 · Accepted solution]

3

[Former Member · Accepted solution]

thanks a lot Avinash for your support

Sujatha Iyer

[Former Member · Accepted solution]

Hi Avinash,

Do you know what other mvt types the "standard w/o distribution "option will exclude?

Thanks,

Sujatha.Iyer

[former_member186100 · Accepted solution]

all movement types with statisitical relevance = 3

[Former Member · Accepted solution]

Thanx avinash i hope this  will solve the issue

can u have a look into the below issue

Route schedule not getting updated  in Purchase order

[former_member186100 · Accepted solution]

unfortunately i have not worked with Route schedule scenario

[Former Member · Accepted solution]

Hi Avinash,

The issue regarding 633 Mvmnt type. The solution which u gave that option did not work. the option Standard W/o Distribution did not work. It say that the option Material Ledger Active gave the closest solution but still they want the solution .

Can u help ?
Any other way ?? to this issue ??

Thanks

Sujatha Iyer

[former_member186100 · Accepted solution]

Hi,

It should work for new transactions atleast , cud u check in ur testing environment , doing single transaction on new material . There it will be easy analysis and it will give clarity about source of seemingly wrong report.

regards

Avinash

[Former Member · Accepted solution]

Hi Avinash ,

Its not working
Any other way out??

[ajitkumar · Accepted solution]

if you have a test sytem you can try the following

in OMO9 you can see the info structure used for inventory . in may be S032

in OLIX you can copy version 000 to another version and delete version 000

in OLI2 load the infostructure S032 after making your required movement not relevant to stat update.

you should give sufficient time to update records( terminate by )

in OLIX make this as version 000 and delete the loaded version

then check

also before load after load etc you can see the( number of )records version wise  in SE11 for the infostructure

you can also refer to help section in LIS under SPRO logistics general

[Former Member · Accepted solution]

I will get back to you after having a look into the checks above mentioned  by you

thanks

[Former Member · Accepted solution]

Hi Ajith,

Can u explain me in a little detail as to how your above check points will help in removing 633..
its confusing .
Can you explain ?

Thanks,

Sujatha Iyer

[ajitkumar · Accepted solution]

with this steps you are deleting existing active  data in the infostructure and recreating by excluding the records with movement type you want to exclude. you also need to make that movement type not relevant for statisitical update in OMJJ before the upload.

i don't know whether it works, logically i feel it should, and this is an option i will  try if i have a requirement like this

[Former Member · Accepted solution]

Hi Ajith,

All the above mentioned Checks by you i think are related to Config?? Right ??

I dont have access to do anything  in Config ?? Some other way out ?? Sorryy for the trouble.

Need Help

Thanks
Sujatha Iyer

[ajitkumar · Accepted solution]

yes, they re in configuration but can be accessed thru those tcodes. if you are using the config path, you can read the help data.

i dont know any other way. this too was a suggestion and hence the emphasis on test server. i have not touched any LIS other than related to PM