Hi,Anyone has an idea why the purchasing MOQ information message does not pop up when a PR or PO does not have the minimum order QTY? MOQ is already defined in Supplier for Purchase Part window. Best Regards,Disal
Invoice text that added at the preliminary stage of the customer invoice is not viewable once the invoice is printed. Invoice text can be added or edited only when the invoice is in Preliminary state. Once Printed, no invoice text can be added or edited. This is to make sure that nothing will change after printing the invoice.After printing the invoice, Invoice text only can be found at the bottom of the printed invoice as the ending text. This cannot be found in the application once printed. This is the intended behavior of the application.
You may have observed that the Campaign QTY cannot be observed in Historical Data tab in Forecast Part window after creating new campaign in forecast client.This is ‘as designed’. The reason is that this view shows the historical data for demand planning (PERIODICAL_TRANSACTION_TAB) this tab only has the historical campaign qty’s. The future campaign qty’s is stored on the FORECAST_DAY_TAB.The budget and Target sales plan numbers is entirely stored in PERIODICAL_TRANSACTION_TAB that’s why future values for these lines are visible in this tab. Budget and Target Sales Plan lines are not supported in other timelines than the standard period version (all historical data in DP is only stored in the standard period version resolution).While the forecast data is stored in day resolution. Future campaigns are stored in day resolutions as is future forecast values.So, it is recommended to use the Legacy client to see the data since here you see all the data both historical and forecast.
This issue is a result of the current technical design. Parts that are set to obsolete/prototype (Demands not allowed) status are filtered out from the Part LOV in the Material Requisition lines. Therefore, the Framework is not able to make a connection to fetch the value for Part Description as the Description is fetched through a reference defined in the entity. This is the reason why the description disappears after the status change in the scenario in question.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
