Skip navigation

AdvisorWebcast.pngMRP Periods of Supply Explained - This one-hour advisor webcast recording is recommended for users of Material Requirements Planning and Supply Chain Planning. The presentation covers Order Policy Code 4 which is designed to be used primarily with high-use/low-cost stable demand items with the system recommending supply quantities based on total demand that falls within a period of days. Additionally, best-use scenarios as well as limitations associated with Periods of Supply are discussed.


For all of the details and a recording of the presentation, please see ADVISOR WEBCAST: JD Edwards EnterpriseOne: Periods of Supply explained (Doc ID 1989974.1).

To save time you can use the Autocash functionality to have the system apply cash receipts to A/R invoices automatically. There are several algorithms available that will apply the cash in different ways:

  • Known Invoice Match With Amount (R03B50D) - Your customer provides you with information to identify a specific invoice, and specifies the amount they want to apply to it.
  • Known Invoice Match Without Amount (R03B50E) - Your customer provides you with information to identify a specific invoice, but does not specify an amount to apply to it.
  • Balance Forward Match (R03B50B) - Your customer does not provide you with any specific information regarding the invoice(s). You apply their receipt(s) to the invoice(s) in sequential order, either the oldest first aka First In First Out (FIFO), or the newest first aka Last In First Out (LIFO).
  • Invoice Selection Match (R03B50A) - Your customer does not provide you with any specific information regarding the invoice(s). The system applies the receipt to a single invoice or a running total based on due date.
  • Combination Invoice Match (R03B50F) - Your customer does not provide you with any specific information regarding the invoice(s). The system applies the receipt to a combination of invoices. You define how many invoices the system selects, in a random order, to find a matching pattern.

 

Here's a summary of the various tasks setting up and processing cash receipts via the Autocash functionality:


Setup:

    1. Determine which algorithm or combination of algorithms you want to use. You can even use different versions of the same algorithm at the same time.
    2. Using Batch Versions set up versions of the chosen algorithm(s) and set the processing options on them as desired.
    3. In Define Execution Lists set up an execution list with the algorithm version(s) in the desired sequence or order.
    4. You can assign this execution list as a default on the customer master records of your clients. You can also put it in the processing options of Update Receipt Header (R03B551) or Apply Receipts to Invoices (R03B50). More on this later.
    5. Determine how you are going to upload the cash records received in a file from your bank into the F03B13Z1. You can use one of these methods:
    6. Set up a version of Update Receipt Header (R03B551).
      1. A custom UBE or process (make sure to check and use the information on how to map the file to the F03B13Z1),
      1. The EDI Lockbox functionality,
      1. The Text File Processor program (P007101)

This UBE will create unapplied cash receipt records (doc type RU) in the Receipt Header (F03B13) and the Receipt Details (F03B14) tables, based on the records in the F03B13Z1. The processing option for Execution List is only used if the field for default Execution List on the Customer Master (F03012) record of the customer is blank.

      1. Set up a version of Apply Receipts to Invoices (R03B50).

    This UBE will process the RUs created by R03B551 or manually created RUs or both, and attempt to apply these to existing, open invoices, using the algorithm version(s) specified on the Execution List.

    The processing option for Execution List is only used if the Execution List field in the Receipts Header table (F03B13) for the unapplied receipt is blank and the field for default Execution List on the Customer Master (F03012) record of the customer is blank, in that order.

    Process:

      1. Upload the receipts into the F03B13Z1.
      2. Run R03B551.
      3. Run R03B50.
      4. Post the resulting batch(es).
      5. Revise any receipts if necessary.


    Post the revisions.

     

    For more information on setting up and processing cash receipts via the Autocash functionality, have a look at the following knowledge articles:

    • How To Set Up and Map Data for Automatic Receipts In EnterpriseOne Accounts Receivable (Doc ID 1458481.1)
    • How To Process Automatic Receipts (Auto Cash) In EnterpriseOne Accounts Receivable (Doc ID 1458442.1)
    • FAQ - Frequently Asked Questions Regarding Automatic Receipts/Auto Cash (Doc ID 945692.1)
    • Troubleshooting Common Errors on Automatic Receipts/Auto Cash (Doc ID 1988280.1)
    • FAQ - Frequently Asked Questions on A/R Interoperability (Doc ID 945685.1)

    NewFeature.pngLogs are an essential part of diagnosing and resolving issues. There are many different types of logs and they take time to collect but in most cases they are essential to finding a resolution. For these reasons the SRDC documents have been created and you may have already seen them but just not realized it.


    Quite simply these are document that clearly explain what specific data (logs, information, table data, screen shots) is required to troubleshoot a specific problem and how to gather the required data.


    SRDC’s are standard knowledge documents with a type of DIAGNOSTIC TOOLS that are based on a specific types of issue e.g. Package Build, UBE etc (just as our other documents are) but they are created using a specific builder to create a consistent look and feel and user experience.


    These documents maybe attached to your Service Request by an Engineer or presented you whilst logging a new Service Request so you know immediately what information is required to resolve your issue and how to generate it. 


    We are constantly adding to the list of SRDC’s but here are some example SRDC’s that exist today:

    • SRDC – How to Generate Logging Information for a Report or Batch Application (Doc ID 1630238.1)
    • SRDC - Data Collection for Troubleshooting a Package Assembly Issue (Doc ID 1931378.1)
    • SRDC - Data Collection for Troubleshooting a Package Build Issue with Tools Release 9.1.5 Enhanced Server Only Package Build Process (Doc ID 1931514.1)
    • SRDC - Data Collection for Troubleshooting a Package Build Issue (for Tools Releases pre-9.1.5) (Doc ID 1931379.1)
    • SRDC - Data Collection for Troubleshooting a Package Deployment Issue (Doc ID 1931381.1)
    • SRDC - Collecting Data For Troubleshooting Issues When Using The Change Assistant Tool (Doc ID 1906687.1)
    • SRDC - Data Collection for Troubleshooting a JD Edwards EnterpriseOne Software Update (e.g. ESU, ASU) Issue (Doc ID 1957734.1)

    For news and information on all things midsize, read the latest Midsize InDepth Newsletter. Note the Spotlight on Oracle’s JD Edwards with information about the JD Edwards Integration Platform and new release announcements.

    Subscribe to and share the Midsize InDepth Newsletter with colleagues.

    NewFeature.pngJD Edwards just released new functionality designed to make production scheduling much easier and faster for Manufacturing customers.

    Watch this video and learn how the Work Center Load Review Calendar provides real-time visibility into scheduled work center loads and available capacity by day, week, and month.

    JD Edwards is continuing its effort of building mobile enterprise applications to empower mobile workers to accelerate business execution on their device of choice.

    For this release, JD Edwards is upping the ante by delivering the first mobile application enabled for disconnected and offline use.

    This release brings the total number of Mobile Applications available for JD Edwards EnterpriseOne to 84. New applications are available on Apple’s App Store, Google Play, and as Archives on the Update Center. Find details about this release here.

    untitled.bmpAdvanced Preferences in Transportation are a powerful tool for automating and streamlining certain critical functions, such as:

    • Carrier selection and mode of transport assignment
    • Rate schedules
    • Distance-based freight rating 
    • Adding accessorial charges
    • Printing of shipping documents
    • And more…

     

    This flexible functionality can be implemented based on individual item numbers and customers, or groups of them, to let the system handle some of the complex decision-making according to sets of predefined rules.  This can help reduce the number of mistakes and oversights commonly seen during shipment planning and activity.

    For more detailed information on how you can improve the efficiency of your Transportation process, see Advanced Transportation Preferences (Doc ID 1209344.1), or view the Advisor Webcast: Advanced Preferences in Transportation (Doc ID 1602309.1).

    Do you ever come across a pesky Accounts Payable batch that just will not post? And it always seems to happen during the most inopportune times, like at the end of a fiscal period or even fiscal year. Well, there is no need to fret!

     

    Posting issues can be caused by a plethora of problems, some of the most common are:

    1. For vouchers, different GL Dates between the Supplier Ledger (F0411) and the General Ledger (F0911) table. If there is a different GL date, the system throws an out of balance because the same transaction in both tables is expected to have the same GL Date.
    2. For vouchers, amounts that do not balance between the Supplier Ledger (F0411) and the General Ledger (F0911). These out of balances can be caused by incorrect amounts in any of the following fields:
      • Amount to Distribute (ATAD) in the F0411
      • Gross Amount (AG) in the F0411
      • Amount (AA) in the F0911.

       3. For payments, an out of balance issue can occur during the post when the Payment Header (F0413) amount doesn't match the Payment Details (F0414).

     

    Another common issue is if the Post (R09801) in interrupted or crashes unexpectedly when running. This may leave your transaction tables (F0413, F0411) and your GL in disarray. In these cases, manual comparison may need to happen to see what was posted and what did not complete, and based on the analysis, the batch can be resubmitted.

     

    For more information, check out our new Troubleshooting guides for posting problems in Accounts Payable:

    • Troubleshooting Non-Currency Voucher Post Failure Errors or Issues Within EnterpriseOne Accounts Payable [Video] (Non-Purchase Order Related) (Doc ID 1993791.1)
    • Troubleshooting Currency Voucher Post Failure Errors or Issues Within EnterpriseOne Accounts Payable [Video] (Non-Purchase Order Related) (Doc ID 1994174.1
    • Troubleshooting Currency Accounts Payable Manual Payment Batch (W) Post Failure – Out Of Balance Condition In EnterpriseOne [Video] (Doc ID 1642947.1)
    • Troubleshooting Non-Currency Accounts Payable Manual Payment With Voucher Match Batch (M) Post Failure – Out Of Balance Condition In EnterpriseOne [Video] (Doc ID 1642889.1)
    • Troubleshooting Non-Currency Accounts Payable Automatic Payment Batch (K) Post Failure – Out Of Balance Condition In EnterpriseOne [Video] (Doc ID 1642828.1)

     

    If you are still having issues with a batch, gather the data as outlined in the corresponding document and create a service request for further help in troubleshooting your issue.

    NeedForSpeed.pngOracle Support knows your time is valuable, and we have tools and features available to help you resolve your product issue as quickly and efficiently as possible. We have incorporated several new features to help speed Service Request (SR) resolution time for common types of software issues.

     

    JD Edwards has resources and tools specifically designed to help you resolve your issue and get answers quickly, and without the time commitment of opening a Service Request (SR). Troubleshooting Assistants and Performance Advisors are just a few of the tools you will find linked in the Successful Service Requests for Faster Resolutions (Doc ID 1993795.1).

     

    No matter how proactive you are, there will still be times that issues occur that you cannot prevent or questions that require answers. As an Oracle customer, you have multiple channels to connect with the Oracle Support team and a multitude of resources to help resolve issues or answer questions. Oracle continues to enhance and broaden the capabilities and tools to help resolve issues faster. The document "Successful Service Requests for Faster Resolutions" outlines best practices when it comes to creating and working with a Service Request (SR) to enable speedier resolution times. The document also overviews our new Guided Resolution tool which uses logic, based on your specific situation to help guide you to existing Knowledge Management (KM) solutions.  Checkout the new document here: bitly to http://ora.cl/7q3

    balance.jpgIn JD Edwards EnterpriseOne,  transactions impacting inventory must create balanced entries in the Item Ledger (F4111) and the General Ledger (F0911) in order to maintain the integrity between these two tables. Examples of inventory transactions can be: Inventory Adjustments, Inventory Transfers, Sales Update for a Sales Order, the receipt of a Purchase order, the completion of a Work Order, etc.

     

    Sometimes, discrepancies occur. It is important to identify and correct these discrepancies to ensure that the Item Ledger and the General Ledger are kept in balance.

     

    The existing Item Ledger/Account Integrity (R41543) report is based on DMAAI setup, which limits its functionality, as the link between the inventory transactions and the previous G/L accounts is lost if users change the DMAAI setup.

     

    New functionality has been introduced in JD Edwards EnterpriseOne Release 9.1 Update 2 that simplifies the reconciliation process between Inventory and G/L by means of the following key features:

    • There is a new flag (GPF1) introduced in the Account Ledger (F0911) table that identifies the records corresponding to inventory transactions. This flag is automatically updated to ‘1’ for the F0911 records created by new inventory transactions.
    • There is a new batch process (Inventory to G/L Reconciliation Update/R41501) that can be used to flag the F0911 records created by inventory transactions that occurred prior to the implementation of this functionality.
    • A new batch process (Automatic Inventory to G/L Reconciliation UBE/R41500) allows to automatically reconcile transactions without a variance.
    • A new Interactive application (Manual Inventory to G/L Reconciliation/P41500) allows users to review, reconcile and un-reconcile the Item Ledger and Account Ledger transactions. Users can select adjusting journal entries to reconcile transactions with variances.
    • Both the Item Ledger (F4111) and the Account Ledger (F0911) will be updated with reconciliation information when transactions are reconciled. In the Item Ledger, the Reconciliation Date will be updated. In the Account Ledger, the Reconciliation Code, Reconciliation ID and Reconciliation Date will be updated.

     

    9.1 Enhancement - Inventory to G/L Reconciliation Process (Doc ID 1678098.1)

    Filter Blog

    By date: By tag:

    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.