Site data – Logistics DC / Logistics Store
Where is the reference site decided when you maintain the article?
--> It’s decided from following place:
1. Overall setting for article master data (reference DC/Store) (WSS1) -- TWPA-VLGFI / TWPA-VLGVZ
the default reference site client wide. when you don’t specify anything and go to logistic view, this is under the default ref site.
2. Sales org and Distribution Chain specific settings (Logistic General –> Basic Data Retail –> Distribuiton chain control) -- V_TVKOV_W-VLGFI
Does REFSITE impacting this?
--> No. (for sure. tested)
The purchasing node in REFSITE only impact the MASS_MARC… ???
| In general you have two options to remove deviations: | ||||
| 1. If you usually use the same value in all dependent sites of a single | ||||
| reference site (global reference DC, global reference store or | ||||
| distribution chain specific reference store), then you should look | ||||
| to maintain also this value in the reference site. By this change | ||||
| all deviations are removed for dependent sites, where no other field | ||||
| still requires the deviation entry. If there are only a few sites, | ||||
| where you still require a different value, then a single deviation | ||||
| for such sites is usually not critical. Especially it would be no | ||||
| reason to fully exclude a field from the copy handling as described | ||||
|
in option 2. |
||||
| 2. If the value for a field is different for most of the sites, then | ||||
| it makes sense to exclude the field from the copy handling by | ||||
| deactivating the "copy field content" indicator as described by you | ||||
| already above. Then no deviation entry is created for new sites, if | ||||
| there is no other fields which requires this. But this has no direct | ||||
| effect on existing data. For this you need to do any change for the | ||||
| article again, so that the article master checks for the validity | ||||
| of the existing deviations and remove them if possible. This step | ||||
| can take a lot of time. If it makes sense, then I can provide you | ||||
| also a special report, which can speed this up by analysing logistic | ||||
| data specific deviations directly without to change the whole article. | ||||
| But for this further analysis of the deviations in your system us | ||||
| required before to see, that this can really help you. Especially | ||||
| the result of the report ANALYSEMABW is helpful there for us. |
--> Report: Z_MABW_CLEANUP