Sunday, April 14, 2019

oracle Fusion Sales orders usage and guide 

1. Order type : is a lookup  to add new values  (seeded : ship ,Return, mixed we can create our own)

2. Manage Assignment Rules : Is a VIB based rules used to write which process need to be assigned  in IF condition we can use the order type any specific values on EFF or any value on the sale order lines.

3. on 19.01 we  have sales agreements, sales channel, sales credit etc on header. 

4. once sales order line moved to awaiting shipping then if we create revision then SO lines will have Blue DOT which means if changes made on the header will not be reflected in SO lines. 

5. Shipping tab : we have request type : arrive on or ship on (ship on is used for Dropship enter the latest acceptable arrive date earliest arrival acceptable date), requested date, ship method, packing instruction, Ware house  or either supplier and site in case of DROP Ship. Ship all lines together will assign to all the lines in the sales order with value DEFAULT.

 6. Shipset in the SO lines is for GOP to schedule lines together and assign a single orchestration process. 

7.we have payment method, payment terms, receivable transaction type  etc. 
if payment term is not provided then SO line progress to AR interface and will be a stuck order. 
to default the receivable transaction type we can use the Pre transformation rule based on order type for example.

8. To default the Values or check validation we can use Rule below on SO lines infusion 

Manage Order Extensions we have at Save & Submit
Manage Processing Constraints (at order creation from Web service or at Save on UI)
Manage Pre transaformation Rules (at order creation from Web service or at Save on UI)
Manage Post Transformation Rules   (at order creation from Web service or at Submit on UI)
Manage Product Transaformation Rule (for addition/ delete a line substitute,)

9. we can revise a sales order and cancel a SO line , modify to some fields.

10 on a Back order SO line we can not make change of Warehouse.

11. we can make a change on the SO line using the Fulfillment workbench with out creation of the revision. 

12. we can split the SO line  using the Fulfillment workbench when SO line is on Manual task : 

steps : 
Unschedule the SO line before status of the line is shipped.
SO line moves to Manual Scheduling required. 
Make a Split on the line and make a change 

13. For Drop ship order if the SO line is failed at scheduling then we can modify using edit button called a override option by providing the  supplier and site along with SSD SAD mandatory. (Other field we can check the box yes.)

14. For SO line in fulfillment workbench we can use the check availability option /GOP work bench.
Steps :
Select the SO line and click on the Check availability button
GOP workbench will open new window
using the Actions we can select the Warehouse to null and any other changes and click submit.
below we can see the all available options.available from different WH and Suppliers.

Note: For this options we need the Sourcing rules set to based on availability option. 
On SO line we need to select the Split is allowed to YES.

15. for Back to Back process on the sales order lines we have supply order status for the fulfillment line once the request is sent to SCO - Supply chain orchestration. Fline status is Awaiting shipping
Reqisition created 
PO Created
PO Receipt pending
Good  Available

16. for sale order lines which are having items ATO model, PTO Model, KIT items and shipset items, covered coverage item will share shipset and same orchestration process.

17. IF the Shipping cost is recorded at the time of shipping then we can see the Cost on fulfillment view > actions> cost and charges. this cost will not be part of AR invoice.

18. ESS: Send shipment Advice  is used when we ship the shipment  with in sales order it will still showing as awaiting shipping only.

19. Manage External Routing Rules help to communicate with the down steam system on below task when the sale order orchestration process reaches.

Manage Web service is used to do the connector configuration.

Ex. Procure  : Doo_ Procure (Connector)

in case of external interface we can use our own user defined connector.

20 . for Dropship sales order lines we can see the Supply PO number, Purchase Requisintion, Po lines, PO Schedule is null once we every time we make change on PO then the PO sequence is update. 

21.  for  sales order line which are dropship we can group the requisition and create one PO, we  can not include  ATO model items as it need PO type PO configured.

22. we can have different sales credit as sale order lines

23. on sales order if we need make change in price for the  item then in Price list we need to enable MPA - Manual Price Adjustment (in back end name is CanAdjustFlag) 


24. we have Freeze price Flag on the sales order header level only  (price , charges & Tax)

25. If we create Sales order from web service with Freeze price Yes then it will not look in fusion pricing even at revision.



 




Saturday, April 13, 2019

orchestration process some key things to remember

orchestration process some key  things to remember  to avoid errors

some thing we need to know so that it will easy the process for creation of orchestration process

1. Only Tasks  we can set it to "Manual" Tasks in the orchestration process
  • Schedule
  • Reserve 
  • Pause  types (SAC types are Event based, Timer, Immediate )

2. We can repeat/ duplicate same task type again like "Schedule" Task once used in the process step 1 then again we want to use it in step 10?
Note : we can create a Alias and then we can use it

3.  SAC - Start After Condition is must and used only  for a Pause task. Pause Rule need to be priority Medium & Release rule need to be at the highest priority


4.  Web service Process to communicate with external systems
  • FTL  - Fulfillment task layer for oracle EBS
  • TTL  - Template Task Layer for other systems  Adhoc
  • OFRS - Oracle Fulfillment Process (XML Tags are different when compared to the task layer fulfillment response composite )


Note: Both  TTL & FTL process uses same task layer fulfillment reponse

5. Internal Fusion Fulfillment systems

  • Schedule - GOP
  • Reserve - Inventory Reservation
  • Invoice  - AR
  • Receive -- Inventory
  • Shipment -- Inventory
  • Return -- Inventory
  • Purchasing --PO
External systems : OTM, GTM, Legacy, any thing outside fusion.

6. Exit Criteria
obtain status from the task status condition which is marked as completed status
for shipping - shipped

7. Do not Checkbox - Use Transaction Attributes very often when not you do not have actual usage

8. Identify the last step of the process and mark "Fulfillment completion"  flag  when your process completes  (B2B, DS, Standard Shipments)

9. Orchestration Process  to use in the OM sales order we need to complete below steps:
  • Validate 
  • Release 
  • Deploy Process
  • when Creation of edit or Revision then Reject Prevision Revision before Release 


10. Change Mode  types
  • Advanced. Process change. Record the state of the orchestration process at each orchestration process step. -- performance issues 

  • Simple. Process change only on the step that receives the change. Record the state of the orchestration process when it starts and at the step where the orchestration process receives the change.

  • None. Don't allow change. Don't record the state of the orchestration process.


11. Parent Process check box when it is used as a orchestration process and if you fail to do those then we can call that process in the other parent orchestration in the branching condition.

12. Process Class : accumulation of  all the status codes and condition which we can use in the orchestration process

13. When Defining Status Condition always try to select the Status values & Expression from the LOV to avoid errors. (Even it is =)

14. Make sure  the at least one status Expression is attached to each Step in the orchestration process.

15. In the fulfillment status conditions please  make use of option Send email notification & Notify External System only when needed

16. We can create a Task Type new while creation of the Orchestration process as an Alias and make use of the same task services defined for the task type.

17. Different Places where the OBR rule is used  on the orchestration process

  • SAC - Start After Condition /  Pause Rule
  • LSC- Line Selection Criteria
  • CP- Compensation Pattern
  • Cost of Change Rule
  • Lead Times Expression
  • Branching Condition
18. when the SO line is on the manual reservation required then we need to provide Warehouse or Supplier details and if any thing not need select clear content and mandatory schedule ship date and submit 

19. when we create a Revision of the sales order then each line will process all the steps from the beginning of the orchestration process attached to that line. 

20.   Orchestration process can have any step we like based on the customer process like start with Reserve, only one step as fulfillment, No shipment , no invoicing etc. 

21. when we define the external routing rule to call the connector, in the IF condition we can use either the task type or task name both will work. 

22.  Reevaluate Flag is on the SAC condition need to be used only when business process is need it will delay he process in checking every time. 

23. Terminate Wait after 30 cycles on the wait task.  


24 Root on the orchestration process tells about the starting level is it order header, line or fulfillment line


25 . when defining the web connector if the integration is ICS then always use the Invocation mode as Business Event

In case of any web service then we need to use below 2 services
Asynchronous: when we do not know the response time and wait is till the response received
Synchronous:  immediate response

26 when using the ICS then while defining the external routing rules always use below conditions

if: Task Type = DOO_Transportation Planning
Then
Set connector Name : Transportation planning (Select from LOV)
set interaction interface type : Service Data
Set Acknowledge Time out :  Day = 0,Hours: 0 Minutes:2, Seconds :0


Pause process (for all the pause steps it is mandatory to raise Pause rule / start after condition)
3 types :
Event Based  -- Event based can be release manually going to the Orchestration Gannt page or  by running the ESS program : release pause  by providing the pause event name
Time Based  -- based on the time provided in the pause task pause will be released automatically
Immediate -- pause will be released immediately.
IPC - accumulate the line for proceeding to the next task.
Example: All invoices consolidate before Invoice or Shipping etc

Default Rule is mandatory(Immediate with high priority) when you raise a Event Based Pause.


After 18.05 version 18.10 onward no need to run  ESS program : Release Planning Recommendation for the  B2B process

Change management : when we use compensation rules it will help to send the do change processing by below said rules
cancel create : cancel the exsisting one and create new one (Ex: Shipping side when we use OTM)
Update : Update only  (Pricing)
Update Create
etc.