cancel
Showing results for 
Search instead for 
Did you mean: 

Assembly Production Order - Credit Check Issue

Former Member
0 Kudos

Hi All,

I have an Assembly production order that is in the process of getting manufactured.

At a later date, the corresponding Sales Order for the Assembly Prod. Order falls under credit hold.

When the Sales Order order is again credit release, a new Assembly production order is getting created and the Old one is automatically getting deleted.

Is there any solution to stop this happening as this is triggering to manufacture the same item again i.e duplicates.

Any insight will be of great help.

Regards,

Bharat.

Accepted Solutions (1)

Accepted Solutions (1)

rammohan_shenoy
Active Contributor
0 Kudos

Bharat,

Please do following. I had similar issue with static assembly orders. Refer SAP note 80891.

In Transaction OVB5 ( VOFM) (Maintain: Requirements & Formulas), choose the menu options "Requirements -> Subsequent functions -> Purch.req./assembly".

The system displays the change view of table TVFO with the following entries:

RNo Requirement SyRoutine System requir.

102 PReq 2 System: BANF

105 Assembly 5 System: Assembly

106 Block construction 0

Remove requirement 105 (replace it with blanks) for processing the subsequent function "Assembly".

Note: Requirement 106 is an identical copy of requirement 105. It contains the credit status check. The line refers to the subsequent fucntion "Set or remove construction block".

After this change, the reference of the sales order to the production order is retained even if the credit status is changed, and in production order, the system status ASSB (assembly lock indicator, ISTAT=I0341) is set or deleted depending on the result of the credit check. The production order has no deletion flag and no new production order is created after a later credit release.

thanks,

Ram

Former Member
0 Kudos

Hi Ram,

Thank You for the Response.....

The solution works...Thanks a Lot, instead of SAP setting DLFL flag, it sets ASSB flag which is good.....

but I am wondering, with this solution during the initial sales order creation if the credit check fails (which could be a genuine credit block and the credit analyst donot want to release the order at all) then also it is creating a Assembly Order with an ASSB block which could trigger manufacturing as ASSB is just an info but doesn't stop anything.

Was the above scenario also addressed in your case ?

Regards,

Bharat.

rammohan_shenoy
Active Contributor
0 Kudos

Bharat,

I think your first question was answered completely.

As far your new question I can remember that status ASSB either blocks release of production order or

GR from production order. It would definately prevent sale order delivery or PGI.

However as a workaround If you need to further control on the production order, you can always create USER Status that gets triggerred when ASSB staus is activated. This user status can then prevent certain business transactions like prod order release or Confirm etc...

Hope this answers your 2nd question. Good Luck.

Thanks,

Ram

Former Member
0 Kudos

Hi Ram,

Thank You.

Yes the questions are answered completely.

Awarded complete points.

I tried certain transactions like, GI, GR, CNF but looks like ASSB is just for information and doesn't stop any further processing of the production order.

However to address the issue in my 2nd question, we created a new routine (copy of 105) but added a condition where SAP deletes the prod. order during the very first credit check when the sales order first gets created.......and from then onwards if again a credit hold happens for the sales order we enhanced the new routine code such that it skips the routine code thereby avoiding any deletion of the assembly production order and just puts an ASSB status in a similiar fashion as it does if we blank out 105.

Once again Thanks for your response.

Regards,

Bharat.

rammohan_shenoy
Active Contributor
0 Kudos

Thanks Bharat.

That was a very good solution you put in place. Appreciate your feedback.

thanks,

Ram

Answers (0)