BizTech Blog

Recently, I arrived bright and early to support the first month-end close after a large client R12 upgrade from 11.5.9 to support closing of the books. The invoices for the month were 10 million dollars, but the revenue in General Ledger was only 5 million and the CFO looked a bit concerned. Where was the rest of the revenue hiding?

When Fusion Middleware Applications are installed there is a default user (weblogic or a specific name that you provide) that is created during the domain creation which acts as a super user for all Middleware Applications. This post walks through the process of resetting the weblogic password in an event that it’s lost.

1. Shutdown Weblogic Server and all associated applications.
2. Set the Weblogic Server environment variables –
   $DOAMIN_HOME/bin/setDomainEnv.sh
3. Navigate to $DOMAIN_HOME/security and rename the DefaultAuthenticatorInit.ldift file.
4. Create an initialization file in the same directory using the below command –
   java weblogic.security.utils.AdminAccount <weblogic_user_name> <weblogic_password> .
5. This will create a new DefaultAuthenticatorInit.ldift file.
6. Navigate to $DOMAIN_HOME/servers/AdminServer and rename the data directory.
7. Repeat step 6 for all the managed servers which are part of the domain.
8. If boot.properties is used, recreate them with the username and password that was provided in Step 4.
9. Start Admin Server and make sure you can login using the new credentials.
10. Start the rest of the services

Note: This process will remove all the user accounts in the weblogic domain and only the new user that is created will be present and act as a super user.

Multiperiod accounting is a flexible, powerful tool available with Release 12 of the Oracle e-Business Suite which allows users to systematically record accounting entries across multiple periods. This post will focus on real world applications of this functionality, and present the detailed steps required to implement the functionality within Payables and Purchasing.

Multiperiod accounting is a flexible, powerful tool available with Release 12 of the Oracle e-Business Suite which allows users to systematically record accounting entries across multiple periods. This blog entry will focus on real world applications of this functionality, and present the detailed steps required to implement the functionality within Payables and Purchasing.

If you are using R12 you may have encountered a requirement to setup all your legal entities with intercompany accounting for each. That is, for each legal entity, whether your setup requires that you configure intercompany relationships for each entity you have, or you are able to use the all other setup, it can still be a lot of work to configure.

In my previous blog entry, I talked about the overall picture of developing a custom Oracle Projects interfacing process. In this entry, I’ll review the steps for creating the initial Project record and associated components. For the Projects Interface Application used as my reference, the main Project record requirements are: Customer; Project Manager; Tasks; Budget (Cost/Revenue)

For those familiar with developing API based interfaces, calling the Create-Project API functions in the same way. For those unfamiliar with API development, prior to the actual API call, inbound data from the third-party application should be assigned to the available API record-fields, for creating the Oracle Project (much like populating the fields of an Interface table). Some fields are required and will cause the Create Project API to fail, returning and error if missing or invalid.

Oracle finally released a reporting tool that reports on the differences in E-Business Suite database objects between one release and another. That's a very useful reference to Tech users to understand EBS dictionary at a module level, but EBS defaults are delivered as seed data within the database objects themselves. What about the differences in this seed data between one release and another?

You have been tasked with developing an interface to AR and you’ve never used Oracle’s Auto Invoice before. What do you do? Unfortunately, at one time I was in this situation. Though I knew the concepts of the process, the real time implementation involved a lot of challenges. The following is for those who have never interfaced invoices through Auto Invoice. My goal is to provide an overall understanding of the process and pitfalls that one should be aware of.

What is Auto Invoice?

All,

In a previous post, I spoke of an organization that needed to create a custom BI Publisher template to accommodate their Canadian bank’s proprietary file format for EFT files in R12. What I didn’t mention was that some of the required data was stored in descriptive flexfields within Oracle. Descriptive flexfields are not included in the Oracle Payments Funds Disbursement Payment Instruction Extract data which is the standard data definition for AP funds disbursement.

As is the case with many organizations, they were concerned that they would have to modify the standard programs to accommodate their bank’s requirements. Their minds were put at ease when they learned that Oracle provided a standard API which allows organizations to add additional fields (i.e. XML Tags) to the XML extract. This standard PL/SQL package was the IBY_FD_EXTRACT_EXT_PUB.

The standard XML file that is generated by the Payment Instruction Extract is organized into 4 hierarchical groups:

1. Payment Instruction – The payment instruction group encompasses the entire file.
2. Payment – The payment group represents a payment to a specific supplier.
3. Document Payable – The document payable group represents the individual invoices that are being paid to the supplier within the payment.
4. Document Payable Line – The document payable line group represents the lines within the invoice being paid to the supplier.