Release Management Schedules

High Level EDI and RLM setups and How to Enter EDI Schedules Manually in Release Management.

We are now going to see how to built Manual Release Management Schedules including the EDI Trading Partners Setups. We will also discuss some of the issue you may get after running demand processor.

Release Management is used to automate customer demand and add it to our sales orders and planning processes.

We will cover one by one from basics to achieve the same. We are here assume that profile option are already setup

Note : Profile options in e-Commerce Gateway: There are system profile options where you define inbound & outbound directories and Other profile options used to enable/disable particular transactions like enabling inbound planning schedules etc. or enable attachment and attachment size or address precedence which determines how a trading partner address will be derived. Each trading partner has a unique address

Step 1) First Step is to define the Trading Partners using e-Commerce Gateway Responsibility.

Specify a Operating Unit : Vision Operation
Group name: Enter a Unique Group name or You can add in already Created Groups

Save your work and after that New Button will get enabled. Click On New.

Step 2) Here Define New Partner Details
 


#Specify A unique Partner name : EDI Customers
#On Assignment Tab, In Customer Specify the customer for which you want to Communicate through EDI
We are here taking example of  "w_Enterprise Devices"
#Specify a site for the customer
# EDI Location:  You have to specify this on customer site and It will default automatically from there as shown below. You need to get it from EDI team and put it at customer site.

Step 3) Now click on Detail Tab

#Transaction type we are taking as : IN: Planning Schedule (830/DELFOR)
#Type is : Planning Schedule
#Translator Code is also given by EDI team
#Document standard we will take as EDIFACT
#Map you can choose form List of Values

Save your Work.

Step 4) Defining and assigning Code Conversion category and Values

A code conversion function provides a method by which trading partner and standard codes can be converted to Oracle E-Business Suite application codes and vice versa. (Reference : Oracle EDI User Guide)

There are predefined categories and you can define your own also. We are not going to cover this in detail otherwise whole topic will divert from its basic aim of showing manual Release Management Schedules processing

This along with interface file definition Completes EDI Setups

Release Management Setups

Before we proceed to RLM setups, we have to complete following additional setups

1) Setup an Item "RLM1234" using Purchasing template
2) Setup Customer item for "RLM1234" and define Cross reference, Take customer as "w_Enterprise Devices"
3) Add item in the price list. Take Price list as "Corporate"
4) Misc Receive this item in Stores Subinventory
5) Create a Sales Order for this item and book it : Order number is 67454

Step 5) Next step is to setup Release Management Processing rules

Navigate to Release Management>Setup>Processing Rules

Click New
Enter Operating unit: Vision Operations
Ship from Org is : V01
Ship To Customer: w_Enterprise Devices
Ship To Address : Customer Location. Note that EDI LOcation code defaulted
Customer Item: RLM1234

Step 6) Now we have to define rules. Theses can be define at

1. Customer Level
2. Address Level
3. Item Level

Where Customer level rules default to Address level and Address level rules defaults to Item level. Item Level rules Override all other rules.

Matching logic is used to match the incoming schedules with already processed schedules. There are seeded and optional attributes

Now click on customer rules.

Demand Management Tab

Click on

#Consume Demand Hierarchy : Shipping, Planning, Sequenced. This Means Sequenced schedules will override the Planning schedules and Planning schedule will override the Shipping schedules. i.e. if multiple schedules are received at same time then what will override what.
# ATS PreHorizon Disposition: This tell us what oracle does with the demand that is already in OM with the date earlier then current date i.e. past due or back order demand
# Default Ship Delivery Pattern: If you have defined "Maintain Ship Delivery Patterns" then you can select them over here

Next Click On Demand Fences

There are three types of Fence Days

Frozen, Firm and Forecast

# Frozen: This Prevent demand processor addition of any new demand in exiting demand. So any change in 1 to 7 Days will be rejected
# Firm: Is available for ship demand and Can be updated.
# Forecast (Order Management). This is demand which is not yet available to ship and placed on the sales orders and can be updated
#Forecast (Planning). This is the demand which is not yet available to ship and is in advanced planning engine and can be updated

Now Click on Order Management

Enter The sales Order Number and Price list
Optionally you can select the In Transit days to calculate the request date.

Next Is CUM Management

CUM Management is used to net off those part which are shipped but not yet reached the customer. CUM Management  Prevents oracle thinking that customer still wants those parts and thus prevent adding  the demand therefore overstating the demand.


#Cum Management Type: CUM by Date. This is how your customer send data to you. Cusomer will reset this annually
#Cum Org Level: Ship To/ Ship From
#Shipment Rule Code: As of Current Shipment

Next is General Tab

Enter assigned supplier code. This is given to us by customer and this is how they have identified us as a supplier.

Save your Work

Step 7) Now click on Address Rule.

A Pop will appear which ask if you want to default from level above. Click yes. Similarly click on Item Rules and click Yes when it ask for Defaulting.

Additionally you can set up ship delivery pattern

Step 8) Now click on CUM Workbench. This is used to handle the time difference when an order is shipped and received by customer

Specify the information as shown above and click Find

Specify the Customer Items and click on CUM Key

Click on Create CUM Keys and in that form enter CUM Start Day. Other information
will default from processing rules setups. Below screenshot will be displayed on successful completion of this step.

Test Case

Entering EDI schedule manually in Release workbench. Clcik on new

Enter required information in Header Section as show in above screenshot

Schedule Num: Give Test Schedule
Type: Shipping
Purpose : Replace
Customer: w_Enterprise Devices
Trading partner etc you can query from LOV

Step 10) Now click on Lines

Enter Org, Ship To, Cust Item and Click Tab

In Line tab

Detail Type: type of demand is it frozen or Firm
Sub Type: Buckets of Demand: Day
Qty Type: Actual
Qty: 10
UOM: Ea
Date Type: Deliver

Save your work

Step 11) Now Navigate to Tools>Submit Demand Processor

Click OK and submit the request. Make Sure Request Completes successfully and check the schedules also

As you can see it proceeded successfully. Click on Lines tab and Demand. you can see the sales order from there

Issues

If any issue occurs, the you can check in Exceptions

some of the issue may be like
1) Item is not on price list
2) Cum Key is not defined
3) API failure due to certain reasons

Thanks
Mandeep
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Please share this knowledge with your friends and subscribe at our blog for more updates. If you have any queries, please participate in our Forum or by leaving your comments below.
------------------------------------------------------------------------------------------------------------------------------------------------------------------

Read More»

Shipping Calendar

How to Work with Shipping Calendars

Suppose your organization actually Ship materials from a warehouse only on particular days. So how to prevent shipping from system. To achieve the same Oracle has provided functionality of shipping calendars. Lets take a test case and see how to define and assign the shipping calendar. Before that you can see in below screenshot that I can able to ship material on weekends also which will stop working after we complete our setup of shipping calendar

Define and Assign Shipping calendar

Step 1) Define calendar

Navigate to OM>Setup>Shipping>Calendar>Enter

Enter a Name of calendar "Shipping" and specify the Quarterly Type.

Click on Workday Pattern and specify 5 days ON and 2 days OFF.

You can also specify shifts and Timings etc if you want.

Next Go to Tools> Built to built the calendar

A request will get fired to built the calendar. Make sure it completes

Step 2) Assign Calendar

Next step is to assign calendar to warehouse. Navigate to OM>setup>Shipping>Calendars>Assign

Enter type as Organization, specify warehouse which is Vision Operations and Calendar usage as Shipping and Calendar code is calendar which we have defined in Step 1 i.e Shipping. Also Assign the site name and calendar code. These are shipping locations

Test Case

Now if you want to ship any delivery on weekend system will give you an error as shown in below screenshot

Thanks
Mandeep
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Please share this knowledge with your friends and subscribe at our blog for more updates. If you have any queries, please participate in our Forum or by leaving your comments below.
------------------------------------------------------------------------------------------------------------------------------------------------------------------

Read More»

Outside Processing Setups and Cycle

OSP Cycle

This post is about Oracle Outside Processing Cycle. Outside processing is used when we don't have in house resources to complete a particular operations. In these cases we send material or assembly for outside processing. In other words we leverage the capacity and specialized skills of our suppliers for the work which we can not perform efficiently in house.

Normally company purchase raw material and perform few operations and then send material outside. we will follow the same example

Setup Steps
1) Create Items : FG1 (Finished Good, Its the main item being manufactured),  RAW1 (Raw Material), OSP1 (Outside processing)
2) Resource Creation : OSPRes1 (OSP Resource)
3) Department Creation : OSP_DEP1  (OSP Department and Assign Resource to Department
4) Define Routings
5) Define BOM

Step 1) First thing is to define Items

Lets define three items FG1, RAW1, OSP1

# FG1 > please use Finished Good Template

# RAW1 > Its a purchased item so use purchasing template.

# OSP1> Its outside processing item therefore use Outside Processing template

In purchasing tab make sure to tick Purchased, Purchasable, Outside processing Item and enter a value in list price. If list price not entered then the cycle will fail at the time of importing the requisitions.

Outside processing Item unit type can be Assembly or Resource

If its assembly and resource basis is item then system will create 1 qty in the requisition for each assembly and if resource basis is lot then system will create 1 qty for Job.

Similarly if you want usage as rate or amount the use resource and like you are buying 1 hour of cutting or painting.

For our case we will take it as assembly

Step 2) Resource Creation

Navigate to Bill of Material responsibility>Routing>Resource

Define OSPRes1 as resource type as Miscellaneous and UOM as HR.

Charge Type take as PO move ( PO receipt automatically generates the WIP Move transaction from the outside processing operation to the next operation on the routing. If PO receipt then you need to manually move to next operation) and basis Item.

In outside Processing region enter our OSP1 Item.

Step 3) Department Creation

Create an OSP Department (OSP_DEP1). Make sure to assign it a location (This is the delivery location used in PO), otherwise you may get an error w

while importing the requisitions

Click On Resources button and assign the resource created in step 2

Step 4) Define Routing

Enter Finished good item in header and In main tab put departments. Click on operation resources and enter the operation resource created in step 2 for OSP_DEP1

Save it

Step 5) Create BOM

Enter Item and components as shown in screenshot above. Save your work

Test case

Now Lets test this setups by Create a job and releasing it. Then import requisition >auto create PO > Receiving

Make sure to Misc receive Raw1 material before starting this

Step 1) Create a Job and release it for this Finished good FG1.  Navigate to WIP responsibility>Discrete>Discrete Job

Change Status To Releases and then Save it

Step 2) Navigate to Move transaction window and enter your job umber in Job field

Seq of Operation is from 10 to 20 and qty as 5. Save it

this will insert data in PO_requisitions_interface_all table and then you need to import the requisition

Step 3) Import Requisition

Switch to PO responsibility and run Requisition Import program

Click OK and submit the request. Make sure request completes and in the output you get a message that Number of approved requisitions created = 1

Some time this request fires automatically base don your setting in WIP Parameters.

If this process fails to create any requisition or error out run PO requisition except report to find out the error.

Step 4) Auto create the PO from the requisitions

Check the requisition in the Requisition summary by putting OSP1 item in item tab and auto create this requisition to PO and then approve it.

Now receive this PO. Here you can see Destination type will be Shop floor and location is same as department's location.

Step 5) Now check the WIP move pending transaction.

When the receipt is made, Purchasing triggered a Move transaction by inserting a record into the
WIP_MOVE_TXN_INTERFACE table. This record is waiting to be processed by the Move Transaction Interface manager. You can check them in pending move transaction table.

This Transaction is automatically processed. Now navigate to Jobs>Operations

You can see in screenshot below there are 5 qty To Move. So we need to perform completion transaction.























Step 6) As OSP is the last step in the routing, so we have to do completion transaction.

Click on Continue

Enter completion subinventory and qty and click Done

Now check the WIP job, you can see the completed qty is 5 and onhand has increased

Thanks
Mandeep
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Please share this knowledge with your friends and subscribe at our blog for more updates. If you have any queries, please participate in our Forum or by leaving your comments below.
------------------------------------------------------------------------------------------------------------------------------------------------------------------

Read More»

MWA/MSCA Personalizations in Warehouse Management System (WMS)

MWA/MSCA Personalizations in Warehouse Management System (WMS)

Form Personalizations was first  introduced in 11.5.10 and now integral part of E Business suite. To perform personalization you don't need major coding skills and they take effect immediately. So they can be used to accommodate changing business needs without much involvement of tech members. They work on site. responsibility and user levels.

Mobile personalization is available for Inbound transaction like Receipt, Put away and Outbound Transaction like Pick, Ship Confirm etc

MSCA Personalization support following pages

1. Mobile PO Receipt page
2. Mobile PO Receipt Information Page
3. Putaway Drop Page
4. Item Load Page
5. Move Any LPN page
6. Manual Load Page
7. Update LPN Page
8. Pick Load Page
9. Pick Drop Page
10. LPN Ship Page
11. Mobile Ship Confirm Page
Source : Oracle Metalink

Steps to Enable Personalization on MSCA

Lets Take an example of making PO receipt page and make Line Number & LPN number Mandatory and "To Loc" locator name to "Locator"

Step 1) Enable Profile options using sys admin responsibility

MWA: Enable Personalization: This profile option controls the enabling/disabling of personalization. If Yes, it means personlization is enabled.

MWA: Cache Personalized Metadata : This personalization Control whether you need to bounce the MWA server before a personalization take effects. its recommended in production instance to improve the performance

we will set these options at User level and Lets take an example of my user id (Apps_user) on vision instance

As this is not production environment we will set MWA: Cache Personalized Metadata as NO and to enable personalization we will set MWA: Enable Personalization as Yes

Step 2) Now using Whse Mgmt Super User, Vision Operations (USA) Navigate to MWA Personalization Framework and query for Mobile PO Receipt Page and Click ON Personalize page

A new page will be displayed as below

Click on the pencil box next to each filed to personalize it

Step 3) Lets take Po Line number first. Click on The pencil Edit Button

In the last field "Required""  where originally it was NO, we made it Yes. Save your work

Similarly for LPN, Make it as Yes and Apply the changes

Step 4) Now click on "To Loc" Pencil edit button.

In Prompt, Change the Function as "Locator" which was originally inherit as "To Loc"

Save the changes.

This completes our Personalization

Test Case

Now you don not need to bounce the MWA server to take this effect as we have set MWA: Cache Personalized Metadata to NO. Lets check the MSCA page

You can see Line Num is now mandatory same as LPN number and To Loc is now changed to Locator

Thanks
Mandeep

Read More»