Skip navigation

Setting up Multi-Plant MRP (P3483) can seem at times a bit cumbersome at times. However, identifying your branch plants is the main criteria for building a supply and demand relationship. Branch Plant Relationships incorporates more of a specific relationship by utilizing the planning family a.k.a. Master Planning Family (IBPRP4).

 

The Master Planning Family is set up for each item using the Item Branch/Plant Information (P41026). Pressing F5 to display the category codes is where the Master Planning Family is identified. When relationships are established based on a planning family, the planning family needs to be consistent across all branch plants in the supply chain.

 

A common misconception is that just the planning family from the demand plant is used and that the planning family does not have to be consistent. With this set up (planning family not the same across the supply chain), MRP will not generate, what we refer to as, a good run.

 

A good start to planning families not being set up correctly or producing a bad run, is when MRP begins planning illogically. For example:

 

1. Inquiring on Supply/Demand Inquiry reveals negative availability as the last record  on the screen.

 

  1. Transfer Order messages will only be received for the highest level branch plants.  Then in order to generate transfer messages for the rest of the supply chain,  the P3483 has to be run again and again (without clearing files) until you get to the end (lowest level) of the supply  chain.

 

There are reports of other strange occurrences when MRP is not set up correctly. However, our main goal is to advise you that MRP will flow and produce what you need with the correct setup.

 

To find more information on Branch/Plant Relationships, review Branch Plant Relationships P3403 (Doc ID 782525.1).

 

Should you have any questions, remember that we are here.

Jane D-Oracle

Bugs, Objects And GSUs

Posted by Jane D-Oracle Feb 23, 2017

Searching for Bugs for Objects in MOS and having trouble?

 

JD Edwards World offers Code Changes for Bugs for each of its releases. For its higher releases, there are Group Software Updates (GSU’s) as well. GSUs are large groups of code changes for all objects that may be downloaded in order to make the release current. The benefit of a GSU is you do not have to figure out what code changes are needed for each objects; they are already grouped.  The benefit of a code change is the ability to apply the code without having to affect an entire release and all its objects, only one or a few objects.

 

If you have trouble searching My Oracle Support (MOS) for Bugs & Objects for the World releases search for the text ‘Bugs & Objects’. Documents are written into excel spreadsheets and can be sorted to view bugs.

 

Just as a reminder, use the following documents to assist in searches along with MOS searches for bugs and GSUs.

 

JD Edwards World A9.4 Bugs & Objects (Doc ID 2005948.1)

JD Edwards World A9.3 Bugs and Objects(Doc ID 1467451.1)

JD Edwards World A9.2 Bugs and Objects (Doc ID 746132.1)

JD Edwards World A9.1 SARs and Objects (Doc ID 745797.1)

JD Edwards World POST A8.1 CU 06 and A7.3 CU 16 Bugs and Objects (Doc ID 746699.1)

JD Edwards World A7.3 and A8.1 SARs and Objects (Doc ID 746698.1)

 

Information on Software Updates Available for JD Edwards World A9.3(Doc ID 1500570.1)

Master Note: Considerations for All Applications After A9.3 Upgrade and A9.3 Update 1(Doc ID 1465427.1)

At some point in time, your staff may encounter production scenarios that require a decision on the type of manufacturing operations required to fulfill specific requirements. Along the same lines, you need to determine which type of manufacturing fits the items structure? Should Process or Discrete manufacturing be used to manufacture your item? Let’s look at both functionalities.

 

There are distinct differences between process and discrete manufacturing, specially on the way that the product is created or manufactured. You need to analyze, in detail, what the objective is so you can define the best method to manufacture your item(s).

 

Discrete manufacturing involves the same structure or functionality where the item is manufactured every time over, most likely, pre-defined operations and raw material(s). The end item is completed into inventory, where then it is ready to be sold or moved. If your company manufactures products that are made up of multiple components and parts, that later you can disassemble, and reassemble, then discrete is the answer.

On the other hand, process manufacturing deals with transforming and converting raw material throughout the entire ‘process’ on the shop floor. The process is identified with an item number however, it is not completed into inventory or unassembled. The outputs or Co/By products can be stocked and can contain more than one item. Process manufacturing is driven by manufacturing recipes consisting of formulas which can create new raw material(s), while discrete manufacturing is linked to a somewhat, pre-defined bill of material.

 

So, ask yourself, what type of manufacturing should take place? Do you have a mix of ingredients that once processed will not be able to go back to its original state? An easy analogy to use when making your decision is as basic as making a pitcher of lemonade. Once the lemons are cut in half and the lemon juice is squeezed, is there a way to put the lemon juice back into the skin again? If the answer is no, then the type of manufacturing would be process manufacturing.

 

What does each functionality mainly entail?

 

Discrete Manufacturing                 Process Manufacturing
-----------------------------                 -----------------------------

Stockable Item(s) Costing              Non Stockable Process Costing

                                                       (Cost is made up of ingredients for Co and By products produced)

Standard/Actual Costing                Standard Costing Only

Maintenance & Repairs                  Recipes and/or Formulas

Shop Floor Control                         Shop Floor Control

Production Planning                       Production Planning

Zero Bill or Batch Quantities          Batch Processing

Product Data Management            Product Data Management

Different Configurations                 Single Process

(line type W)

Forecasting                                    Forecasting

Quality Manufacturing                    Quality Manufacturing

 

Need more information related to JD Edwards World functionality? Refer to your release guide about:

Product Data Management - Discrete Guide
Product Data Management - Process Guide

Shop Floor Control - Discrete Guide

Shop Floor Control - Process Guide

 

Knowledge Management document Index of Information Centers for JD Edwards World (Document ID 1447180.2) contains navigation links to guides and documentation.

Are you running into problems when trying to delete a Purchasing Voucher using Match Voucher to Open Receipt (P4314)?

 

Are you receiving errors such as 0667: Record Has Already Been Voided/Deleted, 2417: Functional Server Header Level Error or if running an older version of JD Edwards World software Error 2521: Inquiry By Voucher Number Required First?

 

If so, then you are not alone.  You have a situation where the purchasing voucher was incorrectly deleted (or voided) using an Accounts Payable voucher program rather than the P4314 - Match Voucher to Open Receipt.

 

When this happens, the accounts payable (F0411) and general ledger (F0911) records are updated, but there is no corresponding update to the purchasing receiver files F43121 & F43121H.  This leaves you unable to delete the “purchasing” voucher as originally intended.

 

Help is available in both Troubleshooting Voucher Match (P4314) (Doc ID 1531063.1) which contains additional details related to these errors and Recovery of Purchase Order Voucher Deleted or Voided in A/P (Doc ID 626788.1) which provides details on how to correct this situation.

 

For details on the proper steps to receive and reverse receipts or match and delete purchasing vouchers, please see Reversing/Deleting Vouchers and Receipts in Purchasing (Doc ID 626785.1).

 

These documents also explain how you can set the processing options of your XT0411Z1 Accounts Payable Functional Server to prevent this from occurring in the future.

As of the World A9.2 release, the new approvals management functionality incorporates new programs, files and processes that accommodate a more powerful and effective purchase order approval process. Compelling reasons to consider implementing the new functionality include, but are not limited to:

 

  • A more flexible set of variables on which to base purchase order approval requests, including:

 

    • Upper and Lower Amount Limits
    • Order Types
    • Cost Centers
    • Account Numbers
    • Foreign Amounts
    • Order Quantities
    • Supplier Address Numbers
    • Buyer Address Numbers
    • Item Numbers

 

  • A more elaborate designation of approvers, including
    • Individual Approvers
    • Groups of Approvers (including and/or and hierarchical capabilities)
    • Substitute Approvers
    • Individuals with Override Authority
    • Individuals with Notification Privileges Only

 

  • Batch e-mail capabilities that allow for:
    • Re-sending of approval notifications
    • Escalated messages
    • Consolidated e-mails
    • Various types of e-mail templates
    • Numerous variables allowed within templates

 

  • A central workbench in which to manage different types of approvals (e.g. purchase orders, address book changes, time cards)

 

If you would like to explore the possibilities, please see Approvals Management for Procurement (Doc ID 889689.1).

The Meter Readings (P12120Z) is located on 9/G1331. You can use the Meter Readings - Z File (P12120Z) processing program to call Meter Readings (P12120) as a batch process and use that data instead of data you enter manually; to create or update the Asset Balance file (F1202) and Account Ledger file (F0911).

 

This program runs Meter Readings (P12120) in the background and uses file Meter Readings Z File (F12120Z).

 

Three processing options as associated with the P12120Z. These are:

 

     1. Enter the version to be used to call Meter Readings (P12120).

 

         If left blank, ZJDE0001 will be used.

  

   ERROR REPORTING:   

     2. Enter '1' to skip printing the error report.

 

         If left blanks, the report will print.

  

     3. Enter the version to be used to call the error report program (P41ZERR).

 

         If left blank, XJDE0013 will be used.

 

F12120Z is meant to replace the video so the user needs to ensure data integrity before running this program. The field ZZACCM in the Z file is designed to allow user to choose which AAI account to use for the record to be processed. P12120 employs the same edit logic over the data read from the Z files.                      

                                                                     

Errors encountered will be written into a log file. A report program is available to print these errors. Account Ledger file (F0911) and Asset Balance file (F1202) records will be generated or updated if no errors are encountered.

  
  
    Jump Start Your Oracle OpenWorld Experience   
  
  
         https://blogs.oracle.com/supportportal/resource/sidebars/sidebar-webcast-collage-v160829-1-400x300.jpg        
  
    Working side-by-side with millions of Oracle users around the world, Oracle Support has developed a keen sense for solutions that work—insights, tips, and best practices.   
  
    Take advantage of our conference sessions, hands-on demos, and special events designed to help you excel in your role and build practical skills. Use this opportunity to network with Oracle Support experts and your peers, all in one place and with one purpose—to help you succeed.   
  
  
     
                 
  
  
  
    Featured Events   
  
  
  
    Meet with Oracle University   
  
    Oracle University offers preconference trainings on Sunday, September 18, 2016. This includes 20 unique, deep-dive training sessions. Choose from sessions that cover the most popular Oracle technology topics or complete a certification exam cram course from our best instructors. Don't miss this one-of-a-kind opportunity.    
  
  
    https://blogs.oracle.com/supportportal/resource/sidebars/sidebar-oracle-u-v160829-1.png   
  
  
  
  
  
    https://blogs.oracle.com/supportportal/resource/logos/logo-mos-white-250x65.png   
    Monday Mix   
  
    https://blogs.oracle.com/supportportal/resource/sidebars/monday-mix-sidebar-image-1.png   
  
  
  
  
    Get in the Mix   
  
  
    Join us at the annual My Oracle Support Monday Mix, Oracle Support's unique customer appreciation event that complements the sessions and demos you'll attend all week at Oracle OpenWorld.   
  
    This year's Mix returns September 19, 2016 at Fang Restaurant in San Francisco, just a three-minute walk from Moscone Center on Howard Street. Engage with Oracle Support executives and engineers over drinks and hors d'oeuvres from 6:15 to 8:30 p.m.   
  
    Admission is free for Premier Support customers. Visit our website for more details.   
  
  
  
  
  
  
  
    Connect Ideas, Get Answers at the Stars Bar and Mini-Briefing Center   
  
    Meet us at the Oracle Support Stars Bar this year and bring your toughest technical or configuration questions on any product. Share your experiences and ideas with our "Support Stars" at Moscone West, booth 3451 on September 19–21. Specialists will be available in everything from hardware systems, to database, middleware, applications, and cloud.   
  
    Discover the latest product features and a wealth of powerful tools, resources, and knowledge to help you manage your applications and technology.     Find out more at the Stars Bars OpenWorld website.   
  
  
    https://blogs.oracle.com/supportportal/resource/sidebars/sidebar-stars-bar-v160829-1-400x215.png   
  
  
  
  

Finding Information in Oracle… can be hard at times but there are many easy ways to help alleviate the work in searching for answers. You can also ensure better searches in My Oracle Support (MOS) and help with understanding and accuracy for service requests.

  • When logging service requests provide a clear, concise description of the issue including all detailed steps to duplicate.
  • Add attachments with screen shots of the program name and number as well as related files in excel format / joblogs and dump in .txt format to help in understanding and clarification of an issue.
  • Has the issue also been tested in the TEST environment against the JDFOBJ (pristine) object and is the issue still able to be replicated?
  • Search My Oracle Support to find answers – Use Key Words to find several types of documents
    • Include a program name/number and related error numbers when searching
  • Also include in your search criteria...
    • Type ‘FAQ’ – Frequently Asked Questions document for topic/program
    • Type ‘Troubleshooting’ – Troubleshooting document for topic/program
    • Type ‘Bulletin’ – Detailed information document on topic/program
    • Type ‘Information Center’ – Shows groups of documents for JDE systems (Ex. Sales, Procurement Information Center)
  • If trying to further understand how to use My Oracle Support and getting it to work well for you, use Oracle Premier Support: Get Proactive! (Doc ID 432.1).
  • Use website Learnjde.com when looking for more on JDE including documentation guides  and click a variety of helpful links if you are a JDE User / Admin / business user or Executive.
  • Use Communities to find answers and conversations regarding topics

How To Get Started In My Oracle Support Communities and Follow JD Edwards EnterpriseOne and World Communities(Doc ID 1561246.1)

 

We look forward to assisting you!

Did you know that there are two methods to attach the work order parts list and routing? It seems that Order Processing (P31410) is the preferred method for attaching the part list and routing to the work order header. This is probably due to Order Processing being a batch program where more than one work order can be processed at a time. But what if you only have one work order that requires processing. Should you run Order Processing (P31410) and wait?

 

There is a second method to attach the work order parts list and routing. This is called Interactive attachment (P48013). Interactive attachment works for one work order header at a time and there is no delay. The parts list and routing are attached immediately.

 

In A73, Interactive attachment could not be run if the standard routing (F3003) contained an Outside Operation where a purchase order is created. However, this was corrected in A9.1 and above. Now, a purchase order is created when attaching Interactively. The only caveat is that the work order routing (P3112) must be attached first.

 

Interactive attachments works from the Work Order Header (P48013). Inquire on the work order using Enter/Change Order (P48013) and press F8. The standard routing file (F3003) is read and when pressing F10 twice, turns the action code of the P3112 to an 'A' for add. Press enter and the routing is created. To create the parts list at the same time, ensure that the second processing option in the P48013 for INTERACTIVE BILL/ROUTING ATTACHMENT, is activated.

 

     INTERACTIVE BILL/ROUTING ATTACHMENT

Enter a '1' to automatically create

the WO Parts List when creating the

WO Routing Instructions on-line. 

 

We highly advise to always attach the routing first and not the parts list. The only time the parts list should be attached first is when no routing exists for the item.

 

No reports are generated when attaching Interactively. If a parts list and routing are required, Order Processing can be run with the first processing option (1a.) of Order Processing (P31410) GENERATION INFORMATION set to a blank. This way, the existing routing and parts list will not be reattached. However, a parts list and a routing will be printed as long as the Parts List Print and Routing Print processing options are selected.

A Direct ship order is used to record the sale of items that you purchase from a supplier who then sends the items directly to your customer. Your inventory quantities and availability are not updated. Both a sales order and a purchase order are created.

 

Direct Ship orders are entered with program P4243 (18/G4211).  The Related Order fields in F4211 and F4311 associate the sales order and purchase order to each other. In the sales order, these fields are found on the detail behind the details (option 1 from a detail line of the sales order), and in the purchase order, these fields are found in the fold of the detail.


By default, the order type for the sales order is SD while the order type for the purchase order is OD.


The order line type typically used for direct ship orders is D. By default, line type D has a D inventory interface, indicating  the system will check the inventory for a valid item number, but it will not update quantities or check availability.


An order line type with a Y inventory interface can be used, allowing use of receipt routing and the writing of Item Ledger records for both the receipt and the ship confirmation. In the case of a lot controlled item, this provides Trace/Track functionality, even though the product was never physically in your warehouse. Functionality described in this paragraph became available in releases prior to A9.3.


It is important to note that changes made to the direct ship sales and purchase orders should be made through P4243. Changes you make to a direct ship order in Sales Order Entry (P4211) will not carry over to the corresponding purchase order. Likewise, changes you make in Purchase Order Entry (P4311) will not carry over to the corresponding sales order.

You can have the receipts program (P4312) update the status of the sales order upon full receipt of a direct ship purchase order line. The sales order line status will not be updated if the purchase order line is partially received.


As of Release A9.3 new processing options were added to P4243 to indicate the next status at which changes can no longer be made to either the sales or purchase order. Associated text has to be entered separately to the sales order or purchase order.  Direct Ship Orders have other unique setup and processing considerations compared to regular sales or purchase orders which are noted in detail in the document Direct Ship Orders (Doc ID 626663.1)

Did you know that keying SHIFT+F9 after entering a Work Order header will display the last entered record?

 

Did you know that most releases are shipped with a fast path word COST that when typing it at the command line, it will take you straight to the daily product manufacturing costing menu G3014?

 

Did you know that pressing function key 11 or 12 in the Cardex will display the Document Number Document Type line above the item number field in the header, allowing user to inquire on all related transactions to an specific work order?

 

Did you know that when a component’s Item Description is highlighted in a Bill Of Materials it is indicating that a substitute item exists? For more information please see How to Use Parts List Substitutions (Doc ID 627299.1)

 

Did you know that when a component’s number in the Bill of Materials is highlighted to indicate that there is an ECO message tied to that item in the Item Master?

 

Did you know that the item number is highlighted in the BOM Inquiry (P30200) program indicating that the component has a related flash message and if the descriptions of items are highlighted that substitutes have been defined at every level of a multi-BOM?

 

Did you know that function key F2 in the Journal Entries (P09101) program with the detail area visible (F4), will switch format display in sequence setup via processing options? This allows user to gather more details for the journal entry without having to exit the J/E.

 

Did you know that as of A9.4, Work Center Costing enhancement generates costs in work center levels where cost is broken down by component cost types? The Work Order Variances (P31804) program will create Journal Entries for variances by operation sequences on the Work Order. Variance by work center compares the consumption at the work center or the material issued and hours reported to the standard material and hours established at the work center level.

 

Did you know that in Parts Availability (P30205) the system highlights the Quantity on Hand field if item location has a Lot Hold Status Code, and when the Quantity Available is highlighted there is shortage for the item?

 

Did you know that the Calendar Window (P00CAL) shows highlighted dates based on user’s preference set up in the Calendar Holidays (UDC table 98/HL)? For more information on setting these dates up see How to Highlight Dates in Calendar Window (Doc ID 628811.1).

If you buy anything at a grocery store then you have seen Advanced Lot Management at work. Shelf Life of a product translates into the expiration date of the item.  In addition there are other dates that can be utilized to manage your lot inventory.  Think about products such as pharmaceuticals, dairy, fresh meat or produce. These items not only have a shelf life and expiration date but may also have Best By Dates and Sell By Dates which are part of lot management.

 

Consider also, these items have manufacturing effective and purchasing effective dates. These dates, for example, can establish a time frame for the purchased goods to be inspected prior to the lot becoming “effective”.  In a similar manner, a manufacturing effective date may be used to delay release of a lot for sale to allow the product to fully mature so the product is not available for sale until the manufacturing process, (including aging, curing, etc.) has been completed.  You do not want to sell something that is immature or not ready to be sold. Therefore, not only are the above dates considered but also immature lots are considered by programs to ensure product does not go out the door prematurely.

 

When selling your inventory, what inventory commitment options are available?

 

Standard commitment methods include:

  1. Committing from locations with greatest quantity first
  2. Committing by lot where the lowest lot number is committed first
  3. Committing by expiration date where locations with the earliest expiration date are committed first.

 

But what if these standard methods do not provide the flexibility you need?  Maybe you would like the ability to establish rules defining how inventory is committed for a Customer, Item or Both.  Or even by Customer or Item Groups.  Your processes may require committing inventory by Lot Expiration, Sell By, Best Before, or other specific dates.  If you could just override the standard commitment method set in Item Branch/Plant Information….

 

As of JD Edwards World Release A9.1, all this is possible using Advanced Lot Management! 

 

Advanced Lot Management combines the new lot fields on the Lot Master, Item Master and Item Branch Plant with Preference Profiles to ship product by Ascending Ship Date Rules.  This functionality is incorporated into the sales order entry, pick slip, inventory commitment and shipment confirmation programs and utilizes the new Last Customer Shipment Inquiry and file, P4239/F4239. 

 

For more on this topic review:

Preference Profiles in Sales(Doc ID 626656.1)

Immature Lot Functionality in Sales Order Management(Doc ID 2049519.1)

Lot Effective Dates - Manufacturing and Purchasing Days(Doc ID 804166.1)

 

Or join us on May 11th for the Advanced Lot Management Preference/ Ship Ascending Dates Advisor Webcast were we will be discussing these topics. You can register for this webcast at JD Edwards World Advisor Webcast Schedule and Archived Recordings (Doc ID 1455377.1).

Do you need to create purchase orders to accommodate sales order demand in one fell swoop? There is new functionality in the World A9.3 release to do just that. Prior to the A9.3 release, the Direct Ship program (P4243) was only geared to accommodate transactions for which goods are supplied directly from your supplier to your customer. As of the A9.3 release, P4243 is equipped to handle stock transactions, that is, to create a purchase order for goods received to inventory prior to being shipped to the customer on a related sales order.

 

In addition to creating back-to-back sales and purchase orders via P4243, the Batch Sales Order Creation program (P40211Z) will also accommodate the creation of back to back orders.

 

Prior to the A9.3 release, if you attempt to create back-to-back orders using a stock line type via P4243, the resulting sales and purchase orders may not be processed properly by the system. The system has been enhanced to orchestrate the back-to-back order functionality, as well as to enhance the drop ship process, as follows:

 

Direct Ship Orders (P4243)

  • Prevent order changes at certain statuses
  • Display requested date for purchase orders in video header
  • Display pick and ship dates for sales orders
  • Invoke the Inventory Commitment Preference (for stock transactions)
  • Accommodate order templates
  • Accommodate order duplication process
  • Default Ship-To address for supply branch on PO (for stock transactions)

 

Enter Receipts (P4312)

  • Accommodate partial receipts by updating order lines on PO and related SO
  • Update inventory receipt location to related sales order
  • Automatic shipment confirmation of related sales order

 

Shipment Confirmation (P4205)

  • Prevent shipment of sales order prior to receipt of related purchase order

 

An extended benefit of the new functionality is the ability to track the location of drop ship items from the time they leave your supplier’s warehouse to their final destination (via receipts routing).

 

For more information about the Direct Ship Order Entry program, please see Direct Ship Orders (Doc ID 626663.1).

COLLABORATE 16 offers the perfect opportunity for JD Edwards customers to explore new product releases and trends including Cloud, Big Data, security IoT, and mobility. JD Edwards customers should attend to hear more on these topics and discover solutions through knowledge sharing and networking with customers facing the same challenges in their organizations.

The majority of MRP service requests received for 2016, pertain to issues within the Branch Plant Relationship (P3403) table. While troubleshooting the Branch Plant Relationship Table, we have come across a startling revelation. The Effective Thru Dates for each branch record contains the Effective Thru Date of 12/31/20.

 

We all know that 2016 is in full swing but can you believe that in just four short years, 2020 will be here? Who remembers back in the 1980's when the manufacturing data dictionary item #CYR (Century Change Year) was implemented to be used as the default for the Effective Thru Date fields? When data dictionary field #CYR contains the value of 20, Effective Thru Dates default to 12/31/20 when this field is left blank. Back in the 1980's when 2020 was the default, we had 30+ years to update the #CYR field. Or, so we thought. The majority of service requests entered still display Branch Relationship Revisions with the Effective Thru Date of 12/31/20.

 

Multi-Plant MRP (P3483) contains processing option 3 in each dream writer version where planning horizon periods are defined. The periods are defined in days, weeks and months. The maximum number of periods in any combination cannot exceed 52 periods. So, let's say that 52 months are added with no days or weeks. This takes MRP out to June 2020. Should the Effective Thru date in Branch Plant Constants contain 12/31/20 as the Effective Thru Date, the branch plant relationship line is only good for another 8 months which is too close for comfort.

 

Back in 2010, JDE introduced a program Effective Thru Date Update (P4028) that runs over 70+ data files where Effective Thru Dates and Expiration Dates are changed for Manufacturing and Distribution programs. The data dictionary field #CYR can be changed to the year of your choice as long as you follow the 100 year rule principal. When running the P4028, the files listed in UDC 40/EF are updated to include a new Effective Thru Date so that your data does not expire.

 

Even though this program has been available for many years, we still see customers that have not run the Effective Thru Date Update. The sooner that this program is run, the less likely issues will exist with invalid Effective Thru Dates and Expiration Dates in Distribution.

 

As a reminder Effective-Thru Dates and #CYR (P4028) (Doc ID 656831.1) explains what this program does for both Manufacturing & Distribution files.

 

Branch Plant Relationships contain default values when adding new relationships, the following information will default if left blank:

  • The Effective From date defaults to today's date     
  • The Effective Thru date defaults to December 31 and reads #CYR for the default year.     
  • The level for the component branch defaults to one  more than the level from the header for the source branch.                                              

 

Keeping your setup tables/files current avoids any future problems where data is no longer valid.


For more information see Branch Plant Relationships P3403 (Doc ID 782525.1).

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see https://community.oracle.com/docs/DOC-1022508 for instructions.