Friday Aug 09, 2013

AR: Why Can't I Inactivate Parties in Accounts Receivable?

Are you confused by Parties versus Customers in Receivables?  Are you wondering how to  inactivate a customer/party using AR forms and screens? 

Back in Release 11.5 the customer was maintained through the Customer Standard form, which was owned by Accounts Receivables.  As the data model became more complex,  the Trading Community Architecture (TCA) product and data model was created.   All applications within the E-Business suite that require interaction with a customer integrate with TCA.  Customer information is no longer stored in the individual applications but rather in a central repository/registry maintained within TCA.

For an insight into the terminology of TCA, check out the following blog entry 

Understanding the Customer Form in Release 12 from an AR Perspective!!

From a current AR perspective, when you create a new customer, you are actually creating a Customer Account.  However, because the data is now kept within TCA, the structure of data must adhere to the rules defined within TCA.  One of these rules is, You can define a Party without creating Customer Accounts for it, but a Customer Account always has to be tied to one and only one Party. In compliance with this rule, when you create a Customer Account in AR, the code automatically takes care of creating the Party associated to the Customer Account for you.

At the AR level, you will only transact at the Customer Account level and never the Party level.  This is why in the Customer form owned by AR, you will not have access to manipulate the status of the Party.  To change the status of a Party you would have to access the data via applications such as: Telesales or Customers Online.  You will still be able to inactivate the customer status in the Create Customer screen, but the related party will still be active until you also change this in these applications.

 In order to understand the specifics of these relationships, we would like to advise you of the following MOS documents which will provide you with specific information and troubleshooting tips 

Customer Form, Party Issue: How To Inactivate / Reactivate a Party? Doc ID 883461.1

Customer Form, Address/Sites: Troubleshooting, How To, Known Issues and Patches Doc ID 1437866.1

Oracle Receivables: Overview of the Customer Form in Release 12 Doc ID 1436547.1

HCM: HRMS Release Update Packs (RUP) for 2013 - Available Now!

Did you know that all of the 2013 HRMS RUPs (Release Update Pack) have been released?  Yes!

Here are the patch numbers for the 2013 RUP releases:

App. Version
RUP Name
 Patch #
Release Date
Release 11i Family Pack K RUP8 14488556 5/3/2013
Release 12.0 HRMS RUP 11 16077077 8/2/2013
Release 12.1 HRMS RUP6 16000686 5/31/2013




These patches can be downloaded from My Oracle Support (MOS).  Be sure to review the README for important prerequisite, patching, and post-install information (including data installer and hrglobal.drv ) BEFORE applying the patch.

Why is the RUP important to your business? 

Keeping up with application of the current HRMS RUP is important so that your system has the latest HR & Payroll features and bug fixes.  Also, the current RUP patches listed above are all a mandatory requirement for Year End processing in the Oracle Payroll localizations delivered by Product Development (known as 'Tier 1') legislation's and US Federal HR products. For more information, review MOS Document.295406.1

What’s included in these RUP patches?

Typically the RUP includes changes for new features or functionality that Oracle Development is releasing at that time.  The RUP also includes bug fixes for various issues that have been discovered & resolved over the last several months since the last RUP update.  Also, depending on your legislation, the RUP may include legislative specific changes or updates which are timely and necessary for staying current with HR and Payroll functionality in your legislation.

For a list of the new features, changes, and bug fixes, review the README documents on My Oracle Support.  There you’ll find details explaining what is being delivered in the patch, as well as important information regarding the application of the patch. These documents include links to legislative specific README notes, where you can also review what has been delivered specifically for your legislation.  As mentioned before, review the README information BEFORE applying the patch.

Here are the README documents which are available on My Oracle Support (MOS) for the 2013 RUP releases:

  • Doc ID 1540662.1  About Oracle 11i HRMS Family Pack K Rollup 8(RUP8) (14488556 11i.HR_PF.K.DELTA.8) - Global
  • Doc ID 1564126.1 Oracle Human Resources Management Systems Readme, HRMS Release Update Pack 11 Release 12.0
  • Doc ID 1549442.1  Oracle Human Resources Management Systems Readme, HRMS Release Update Pack 6  Release 12.1


Are there any issues with applying these latest RUP patches?

Yes, please be aware that there could be some issues that were discovered after these RUP patches were released.  There is a ‘known issues’ document for each release version, to give you a heads-up on what might impact your environment.  So be sure to review these documents as well, in conjunction with the patch README documents.

  • Doc ID 1538593.1  Known Issues on Top of Patch 14488556 - 11i.HR_PF.K.DELTA.8 (HRMS 11i RUP8)
  • Doc ID 1538635.1 Known Issues on Top of Patch 16077077 - R12.HR_PF.A.DELTA.11 (HRMS 12.0 RUP11)
  • Doc ID 1538636.1 Known Issues on Top of Patch 16000686 - R12.HR_PF.B.DELTA.6(HRMS 12.1 RUP6)


So don’t delay! Year End processing is just around the corner for some legislations, so you want to be prepared by having the latest RUP patch already tested & applied! If you have any issues or questions when applying the RUP patch, please do a Knowledge search on My Oracle Support (MOS) , and review the known issues documentation.

As always, if you can’t find the solution there, please log a new Service Request for assistance from Oracle Support.


HCM: My Oracle Support (MOS) Not Just for Technical Users

This is a shout out to Functional Users!

Did you know that My Oracle Support (MOS) is not just for technical users, such as your IT Team (i.e. System Analyst, Software Engineers, and Developers) or for use only by your Support staff? 

My Oracle Support or MOS is for anyone who utilizes licensed Oracle Applications.  To get a Oracle MOS account simply go to the following - support.oracle.com - where you will be asked to register for your personal sign-on.   Registering is as simple as supplying Oracle with an eMail address, setting your password, and providing some personal information including your name and company name.  Oracle will respond to the email provided with a verification link to continue Registration. For additional information on MOS Registration and Setup, please see the MyOracleSupport Quick Reference Guide.

Your next question, as a customer, is "What now? How can I, as a Functional Contributor, use My Oracle Support?" Isn't MOS just used to log and track service requests and to download patches?

Well the answer to the second question is, No!   My Oracle Support (MOS) provides functionality and collaborative tools that are just as useful to our functional colleagues, as they are to our technical ones.  The most important tool for our functional user is the ability to research the following:

Oracle Knowledge Documentation Library

Oracle provides a rich set of documentation for every Oracle product. These documents have an immense amount of knowledge for each product that Oracle provides. These are dynamically evolving documents and contain a multitude of different types of information, such as:

  • Problem Documents - which describe a problem, cause, and solution
  • FAQ Documents - which provide a compilation of questions and answers for a particular subject area
  • How To Documents - which provide Q & A, or 'How To' perform a specific task or function within an application
  • Reference Documents - which document a procedure or reference information
  • Troubleshooting Documents - which explains how to diagnose/debug a complex issue
  • White Papers - which are authoritative documents usually created by development describing a specific functionality

Next time you encounter an issue within the Oracle applications,  I would strongly suggest that your first step in finding the solution of your problem is to search Oracle's Knowledge Documentation.  It is possible that you could resolve your own issue rather then waiting on your internal support team to contact Oracle for you. 

For HCM related Knowledge, I would recommend starting with the following:

This document provides you with a starting point for all HCM Products, and allows you to drill down into documentation specific to an application or function. 

Additionally, from My Oracle Support, one can review Online Documentation, Lifecycle Advisors, and Oracle's Get Proactive Portfolio.

An additional resource is the My Oracle Support Community (MOSC) forums which are specifically designed for Oracle's contracted customers only.  In this community forum, you can post your questions with confidence that they will be answered in a reasonable amount of time. This is a community forum and you are welcome to answer other community members' postings as well! (Read Kenn's Proactive blog Why Use My Oracle Support Community (MOSC)).

act-nowjpg.jpg

Get your MyOracleSupport (MOS) Account Setup Today!


About

Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.

Stay Connected

Twitter

Search

Archives
« August 2013 »
SunMonTueWedThuFriSat
    
2
3
5
6
10
11
14
17
18
23
24
25
26
27
29
30
31
       
Today