Error while running deployment optimizer- /SAPAPO/SNPOPT098

[Former Member]

Hello,

I am running deployment optimizer and getting the below error- "The demand for product P at location D001 cannot be fulfilled: There is no initial stock, no production, no transportation lane, and no external procurement. Moreover, it could be the case that a transportation lane exists, but the source location cannot fulfill the demand"

Below is how my model looks-

Planning bucket- weekly

Demand at D001 on week W3 for prod P= 1000

after running SNP (heuristics/Optimizer) --

PReq (Dist receipt planned ATP cat AG) at D001 on W3 for Prod P from source location L001= 1000

Dist demand Planned (ATP Cat BM) at source location L001 on W3 for Prod P= 1000

Production planned (ATP Cat EE) at source location L001 for Prod P on W3 = 1000

After this, when I run deployment optimizer, I am getting the mentioned error.

Any pointer would be of great help.

Regards

Manotosh

[rajkj]

Hi Manotosh,

Please check the ATI and ATR settings (either your location product master or location master record). ATI - ATD quantity to issue

ATR - ATD quantity to receive

You need to assign valid category groups to these parameters to drive the deployment.

Thanks,

Rajesh

[Former Member]

Hi Rajesh,

I maintained ATI and ATR in the prod/loc at both the source and destination locations. Maintained pull, push horizons as 90 days. Then I took deployment heuristics run (/sapapo/snp02) with deployment horizon as 120 days.

There are two stock transfer PReqs of 1000, 1000 for W1 and W2 at the destination location D001. There is a stock in hand Cat CC) of 2000 in the initial bucket at source location L001. Hence ATR of 2000 and ATI as 1000 (W1), 1000(W2) (Dist Demand Planned BH) at L001. When I run deployment heuristics at the source location L001 with destination location as D001, only one of the STR PReq of 1000 gets confirmed by deployment and gets changed to DEP: PurchReq. The other one is not confirmed even though the ATR was 2000.

Why only one PReq gets confirmed by deployment?

Someone suggested to delete ATP Cat BH from ATI cat group and take the deployment run. After doing this, both the STR PReqs were confirmed by deployment as desired.

What has changed by deleting BH from ATI to give desired results?

Any pointer would be of great help.

Regards

Manotosh

[rajkj]

Hi Manotosh,

SNP Deployment, by default, considers the distribution demand from destination location.

Why only one PReq gets confirmed by deployment?

Since you maintained BH in ATI cat group at source, then total demand considered was 1000 (from destination location) and 1000 (source location, in spite of same order) i.e. there was demand duplication. Due to this reason, the deployment heuristic confirmed only the first STR.

What has changed by deleting BH from ATI to give desired results?

When you deleted the cat BH from ATI cat group, the system considered only the distribution demand from destination location. So, the demand duplication was eliminated and hence, the deployment was able to confirm both the STRs.

Thanks,

Rajesh

[Former Member]

Hi Rajesh,

I would agree to your point to an extent. In case there is a demand duplication, the ATI in W1at the source location L001 should show 1000+1000 = 2000. However, in this case, the ATI is still 1000 in the first bucket (W1) and 1000 for next bucket (W2). hence the initial ATR of 2000 should match with W1 ATI of 1000 and W2 ATI of 1000 and should confirm both.

After deleting BH from ATI, the ATI at the source location for W1 and W2 becomes zero.

Regards

Manotosh

[rajkj]

Hi Manotosh,

As mentioned earlier, the system (both deployment and TLB) will consider the distribution demand from destination location without considering the ATI (which is location specific). So, ATI can't explain this element.

By the way, how you checked the ATI quantity?

Thanks,
Rajesh