Thursday, 4 April 2019

JDE WO Process Flow

WO Process Flow:

1). WO Entry P48013 - Status 05 --> Row Exit

2).  Attach Part List P3111

3). WO Issue P31113  - Status 45

4). WO Completion P31114  - Status 95(92 for Partial Completion) 

WO Issue Types

Manual issueThe system deducts materials from inventory when you enter the issue transactions on the Inventory Issue Revisions form.
PreflushingYou set a processing option for the Order Processing program (R31410) to deduct materials from inventory automatically when you process a work order.
BackflushingThe system deducts materials from inventory when items on the work order are reported as complete. This deduction method might occur when you report partial completions throughout the production process or when you report full completions at the last routing operation.
Super backflushingThe system deducts materials from inventory automatically at operations that are defined as pay points throughout the routing when the pay points are reported as complete or partially complete. The Super Backflush program (P31123) enables you to simultaneously backflush materials and labor hours, and report items that are complete at an operation

Friday, 1 February 2019

Purchase Order Approval Setup and Flow

Purchase Approval Setup and Flow

Step 1: Create Approval Route Code
P43008 - Approval Route Code Setup
Enter the Order Type, Amount From, Responsible Person

Setup B/P Constant, Enter the Newly created Approval Route Code  and Save

Setup Processing Option in P4310--> Approvals--> 1. By Branch Plant 2. Next Status

Step 2: Transaction
P4310 - Create the PO using the Application for above B/P, the order will go for PO Approval Request.

Step 3:
P43081 - inquire the PO and approve or reject the PO after review. 

Step 4:
P43070 - Held Order Application .
F4209 is the base table for Held Order Application.

Friday, 25 January 2019

Modal & Modless Form Connection

Modal:

Modal interconnections enable the user to view only one form at a time. After the child form begins, the user cannot access the parent form until the child form is closed.
Additionally, the data connection between the parent and child is usually static. Input data structure items are populated when the child form is launched, and output data structure items are populated when the child form closes. Parent form ER that follows a modal form interconnection call executes after the child form is closed.
In addition to static data connections, you can create dynamic form interconnections. A dynamic form interconnection enables you to call a form by passing the application and form ID. A dynamic form interconnection is always modal.
Modeless:

Modeless interconnections enable the user to view multiple forms at the same time. After the child form is started, users can switch back and forth between the parent form and the child form. Additionally, data changes on a parent or child form are immediately reflected in all other open forms in the connection.

Modal is the default interconnection type. Modal interconnections are appropriate when you want to lead the user through a particular process in which a number of values must be input in a specific order. In this case, you want the user to completely fill out each form before moving on to the next one. Add and copy functions also lend themselves to modal processing because you want the user to complete the function before going on to others.
Modeless interconnections are valuable when the user needs to view or update a series of data records. Avoid using modeless form interconnections if both the parent and child forms should be presented to the user at the same time. A power form is more appropriate in this case.
The parent form in a modeless interconnect must be a find/browse form. The child form type can be fix/inspect or transaction forms (header and headerless detail). When the user updates a record on the transaction form, the parent find/browse form automatically reflects the change.
When the user closes the parent form, the system closes all its modeless children forms.
Parent form ER that follow a modeless form interconnection call execute immediately instead of waiting for the child form to return.

Repost Programs - Sales, Purchase, Work Order

1). R42995 - Repost Active Sales Order
2). R43990 - Repost Open POs
3). R3190 - Repost Open Work Orders