Credit Check Hold Setup

In this Post, we will see how we can apply Credit Check Rule for a Customer.

Credit Hold: In the Customer Standard form when the 'Credit Hold' check box is checked, all orders for the customer will go on Credit Check Failure hold without going through the credit check logic.

Credit Check: In Customer Standard form when the Credit Check check box is checked, the Credit Checking program applies the Credit Check Failure hold after checking the credit worthiness of the customer and applies the hold only from booking onwards.

The Credit Check Rule can be used at the following points in the Order Life Cycle. The same credit check rule, or different credit check rules, can be defined for all four (4) of these phases:
1. Ordering
2. Picking
3. Packing
4. Shipping

Sales Order Level Hold: Order level credit check uses exclusively header level information ignoring different bill-to sites detailed at line level. Order level credit check is performed for the header 'Bill to Site'.

Sales Order Line Level Hold: Line level credit check uses data at the sales order line level. When an order line fails credit check, any remaining lines grouped with the same 'Bill to Site' are also placed on hold.

Credit Check Steps:
a) Credit Limit Setup: At Customer Acount/Bill-To-Site Profiles level, check the Apply hold checkbox and give the profile amounts in the respective currency.
(N) Order Management -> Customers -> Standard

b) Credit Rules Setup: Create a credit check rule at Sales Order level because we want to apply Credit Check Rule at Header Level.
(N) Order Management -> Setup -> Rules -> Credit



c) Transaction Type Setup: Here, we need to enter the Credit Check Rule at Order Level. Either create a New Transaction Type or open the existing Transaction Type to apply the Credit Rule information.
(N) Order Management -> Setup -> Transaction Types -> Define



d) Payment Terms Setup: Enable “Credit Check” check box on the payment terms that you are using.

(N) Order Management -> Setup -> Orders -> Payment Terms



Now, create a New Sales Order and select the same Customer, Payment Terms & Transaction Type which we have use in Credit Check Setup.

If the Sales Order amount is greater than the amount which we have defined for that Customer then a Hold will be applied at SO Header Level.

Once you BOOK the Order or add a New Sales Order Line to an existing Booked Sales Order then you will get a message saying that Hold is applied at Header Level because of Credit Check Setup.

You cannot Pick Release any Sales Order Line unless or until you remove the Sales Order Header Hold manually.

Kit Setup for the Sales Order Transaction

In this post, I will try to explain about KIT SETUP using Inventory & BOM and w'll do a simple Sales Order Transaction using that Kit Item.

Before starting the Setup, please check the below points:
1. Make sure, Master Org is defined in BOM Parameters.
2. Make sure, Master Org is defined in "OE: Item Validation Organization" profile option.

Steps:
1. Define a Kit item as KIT_ITEM, using Kit Template, with item attribute PICK COMPONENT.

2. Define two items KIT_COMP_1 and KIT_COMP_2 as Purchased Items which will be INCLUDED in Kit (i.e., KIT_ITEM) using BOM.

3. Add KIT Item and INCLUDED Items in the Price List.

4. Create BOM in Master Organization using KIT_ITEM and assign two items KIT_COMP_1 and KIT_COMP_2 in it with quantity 1 each.

5. The above created BOM should be copy to the Inventory Organization.


6. Create Sales Order for KIT_ITEM with quantity 1.

7. Book order and check if included items are shown via TOOLS -->show line detail.


8. Go to Shipping Transaction Form, here we can see INCLUDED items with status "Ready to Release" and you will not find Kit Item because KIT Item is not Shippable.

9. select INCLUDED Items and Launch Pick Release.

10. Select Delivery Number and do Ship Confirmation. Message displays "Delivery Successfully Ship Confirm".

Processing Constraints

In this Post, I will try to explain you about the Processing Constrainst by giving you an example using the navigation.

Processing Constraints allow Order Management users the ability to control changes to sales orders, at all stages of its order or line workflows to avoid data inconsistencies and audit problems.

From Order Management super user responsibility, we’re going to create a constraint which will prevent creation of sales orders or Sales order Line when ever user is selecting Warehouse 'ABC' from a specific responsibility called "Order Management Non-ABC".

Creating a Validation Template. A Validation Template names a condition and defines the semantics of how to validate that condition. Validation templates can be used in the processing constraints framework to specify the constraining conditions for a given constraint.
1) Navigate to Setup > Rules and open the Validation Templates Form. Here, create a new validation for our Warehouse.
2) Enter Entity as Order header and Template name as 'ABC Org' and give the short name as 'ABC_Org' and select the Validation Type as 'TBL'. And enter another line for Entity as 'Order Line' because we need to put restriction on both Sales Order as well as on SO Line.
3) Now, select Column as 'Warehouse' under Validation Semantics and select Validation Operation as '= (Equal To)' and Value String as 'ABC'. Save it.

Now, we will create Processing Constraint for Entity 'Order Header' to put restrictions on creation of Sales Order.
4) Navigate to Setup > Rules and open the Processing Constraints form.
5) Once you’re in the Processing Constraints form, search for application “Order Management” and entity 'Order Header'.
6) Now, click into the Constraints block and create a new record with an operation of “Create” and user action “Not Allowed” and leave other options as default.
7) Now, enter any Group Number let say '101'and select the scope as 'Any' and Validation Entry as 'Order Header' and Record Set as 'Warehouse' and validation template as 'ABC Org'.
8) Give a message to the user saying that "You are not allowed to create Sales Order or Sales Order Line".
9) Now go to the Applicable Tab and select the “Constrained responsibilities” radio option, we now have the ability to pick and choose which responsibilities to apply this constraint. Here, select our responsibility "Order Management Non-ABC".

Now, create a new Constraints for Entity 'Order Line' to put restriction on creation of Sales Order Line.
10) Once you’re in the Processing Constraints form, search for application “Order Management” and entity 'Order Line'.
11) Repeat the steps from 6 to 8 and save it.

Now, if any user is trying to create a Sales Order or Sales Order Line using "Order Management Non-ABC" responsibility then they will receive a message saying that "You are not allowed to create Sales Order or Sales Order Line".

Difference between a Batch and a Delivery

A Delivery can have multiple SO Lines where as a Batch or Pick Release Batch can have multiple Deliveries ( or contains the deliveries that you are packing).

batch_id is referring to the Pick Release Batch and delivery_id is referirng to the Delivery Name.

Creating a Customer at the time of creating a Sales Order

Set the Profile Option "OM: Add Customer" either at Site Level or Responsibility Level based on your requirement.

The above profile option will allow you to create Customer at the time of creating a Sales Order.