JD Edward's Interview Questions

  Commitment Types in JDE Inventory commitment in JD Edwards EnterpriseOne can be classified into three types: Soft Commitment , Hard Commitment , and Future Commitment . Each type is determined by specific processes and system configurations. Soft Commitment Does not specify a particular location for inventory removal. Uses the primary location as the default at the time of order entry. Hard Commitment Typically occurs during the Print Pick Slips process ( R42520 ) but can be triggered at any stage in the sales order process by running Inventory Commitment ( R42997 ). Specifies a location ( SDLOCN ) or lot ( SDLOTN ) other than the primary in the Sales Order Detail (F4211) during Sales Order Entry ( P4210 ). Future Commitment Applies to orders with a future Promised Ship Date (PPDJ) set during Sales Order Entry ( P4210 ). Controlled by the Specific Commitment Days (COMH) field in Branch Plant Constants (P41001) . Requires running the Re-Commit Future Order...

  Sales Update Process in JDE The Sales Update process is a critical function in JD Edwards EnterpriseOne (JDE) for integrating sales transactions with other systems. Below is an overview of its purpose, functions, table updates, and associated DMAAIs. Purpose of Sales Update The primary goal of the Sales Update process is to bridge the sales system with other EnterpriseOne systems, ensuring seamless data flow and accurate record-keeping. Key objectives include: Integration with Financial Systems : Creating journal entries in the General Ledger (F0911) file. Generating receivable records in the Accounts Receivable (F03B11) file. Inventory Updates : Updating the item's on-hand quantity, if not already adjusted during Shipment Confirmation (P4205) . Sales Order Closure : Closing out the sales order and marking it as complete. Data Purging and Archival : Moving closed sales orders to history files, depending on processing option settings. Files purged o...

Q1: Explain the Sales Process with Program Numbers The typical sales process involves the following steps and corresponding programs: Sales Order Entry : Program: P4210 The sales order comprises a header and details : Header Information : Stored in table F4201 (Sales Order Header file) and includes branch plant, customer details (sold-to and ship-to), order date, payment terms, and shipping information. Detail Information : Stored in table F4211 (Sales Order Detail file) and includes item number, quantity, price, promised ship and delivery dates, etc. Multiple line items with similar details can exist. Additional Features : Use advanced pricing to access the price breakup screen and manually override prices if necessary. Inventory can be hard committed during order entry. Last/Next Status: 520/540 Credit Check : If the order amount exceeds open credit, the order is put on hold. The credit and collection department can release the hold. Print Pick Slip : Program: R42520 (Batch appli...

Many a time this type of situation arises when an existing employee of the company, need to be hired for different position in same company for different Business unit. Many of you think that it is very easy process, We can just go to Employee master and change the details like, Home Business Unit, Security  Business Unit, Job title, etc. But this is not the correct way of doing this process. the correct way process is listed in steps below: Go to employee master, find the employee  whom you want to hire for different Position, select the employee. On employee information form, enter Termination Date, and select move to Applicant pool, this will mover employee data to applicant master. Go to Applicant master (P08401), find the same address number as address number will be the same as it was in Employee master. Add the applicant to the requisition.  Click on Hire button on Applicant master, enter requisition number and select status as IF-...

Go to processing option of Requisition Information (P08102). Verify that #2 Address Number of Default Approver and #3 Address Number of Default Recruiter is filled with valid address numbers. If still problem persists Goto Object Management Workbench (OMW) Search for REQAPPRVL in Workflow modeler Verify that Address number field in the recipient rules must be blank (no spaces also). Now Save it. Verify that now Default approver is getting mesesage for approval. If problem still persists Log a call to Oracle Support or Comment here to this post or email me at a.shukla2810@gmail.com.

Queue Up for Token -OMW automatically releases the token during a status change defined in the Object Management Configuration application. An e-mail is sent to the developer of the next project in the queue when the token becomes available. Inherit Token -The project inheriting the token must be at the same project status as the project holding the token. An example might be if one developer already had an object in their project and another project needed to make a modification to this same object. The second project could inherit the token from the first project and then check out the object when the first project checks the object back in.. Release Token- A developer can release a token manually. Typically, you want the system to release the token at the designated status change. Releasing the token manually should only be done when no modifications have been made to the associated object or when the modified object will not be checked in. Switch Token- A develop...