Customers are the core of the Order-to-Cash (O2C) cycle in Oracle Applications R12. Managing customer data efficiently is critical for processing sales orders, invoices, payments, and overall financial reporting. While customer records can be created manually through the Oracle Receivables (AR) forms, many organizations prefer using APIs for automation, bulk uploads, and integration with external CRM or ERP systems. Order-to-Cash (O2C) cycle In this tutorial, we will explore how to create a customer using an API in Oracle Apps R12, covering the key API package, required parameters, and a practical example to help you automate customer creation. how to create a customer using an API in Oracle Apps R12 Why Use an API for Customer Creation? Automating customer creation through APIs in Oracle Apps R12 provides several benefits: Bulk Processing: Handles large volumes of customer data efficiently.Integration: Connects seamlessly with external CRM, web portals, and third-party applications.Accuracy: Enforces Oracle’s built-in validations to reduce manual errors.Time Efficiency: Eliminates repetitive data entry tasks.Consistency: Ensures data is structured uniformly across different business units. Bulk Processing: Handles large volumes of customer data efficiently. Bulk Processing: Integration: Connects seamlessly with external CRM, web portals, and third-party applications. Integration: Accuracy: Enforces Oracle’s built-in validations to reduce manual errors. Accuracy: Time Efficiency: Eliminates repetitive data entry tasks. Time Efficiency: Consistency: Ensures data is structured uniformly across different business units. Consistency: API Package for Customer Creation Customer data in Oracle Apps R12 is managed through the Trading Community Architecture (TCA) model. Oracle provides the HZ_CUST_ACCOUNT_V2PUB API package to create and manage customer records. Trading Community Architecture (TCA) HZ_CUST_ACCOUNT_V2PUB HZ_CUST_ACCOUNT_V2PUB The most commonly used procedures include: CREATE_PARTY → To create the customer party (entity such as individual or organization).CREATE_CUST_ACCOUNT → To create the customer account linked with the party.CREATE_CUST_ACCT_SITE → To create customer account sites (addresses).CREATE_CUST_SITE_USE → To define site uses (e.g., BILL_TO, SHIP_TO). CREATE_PARTY → To create the customer party (entity such as individual or organization). CREATE_PARTY CREATE_PARTY CREATE_CUST_ACCOUNT → To create the customer account linked with the party. CREATE_CUST_ACCOUNT CREATE_CUST_ACCOUNT CREATE_CUST_ACCT_SITE → To create customer account sites (addresses). CREATE_CUST_ACCT_SITE CREATE_CUST_ACCT_SITE CREATE_CUST_SITE_USE → To define site uses (e.g., BILL_TO, SHIP_TO). CREATE_CUST_SITE_USE CREATE_CUST_SITE_USE Together, these APIs allow you to create a complete customer profile programmatically. Key Parameters Here are the main parameters you will work with in customer creation: p_party_rec – Holds customer party information (like name, type, tax ID).p_cust_account_rec – Stores customer account details.p_cust_acct_site_rec – Stores address details for customer sites.p_cust_site_use_rec – Defines usage for the customer site (billing, shipping, etc.).x_party_id, x_cust_account_id, x_cust_acct_site_id, x_cust_site_use_id – Output parameters that return IDs for the created records.x_return_status – Status of execution (Success/Failure).x_msg_count / x_msg_data – Error or validation messages. p_party_rec – Holds customer party information (like name, type, tax ID). p_party_rec p_cust_account_rec – Stores customer account details. p_cust_account_rec p_cust_acct_site_rec – Stores address details for customer sites. p_cust_acct_site_rec p_cust_site_use_rec – Defines usage for the customer site (billing, shipping, etc.). p_cust_site_use_rec x_party_id, x_cust_account_id, x_cust_acct_site_id, x_cust_site_use_id – Output parameters that return IDs for the created records. x_party_id, x_cust_account_id, x_cust_acct_site_id, x_cust_site_use_id x_return_status – Status of execution (Success/Failure). x_return_status x_msg_count / x_msg_data – Error or validation messages. x_msg_count / x_msg_data Steps to Creating a Customer Via API in Oracle Apps R12 To create a complete customer, follow these steps: Create the Party – Define the customer as an organization or individual.Create the Customer Account – Link the party to a customer account in AR.Create Account Site – Define addresses such as billing or shipping.Create Site Use – Specify how the site will be used (e.g., BILL_TO, SHIP_TO).Validate and Commit – Check the return status and commit changes if successful. Create the Party – Define the customer as an organization or individual. Create the Party Create the Customer Account – Link the party to a customer account in AR. Create the Customer Account Create Account Site – Define addresses such as billing or shipping. Create Account Site Create Site Use – Specify how the site will be used (e.g., BILL_TO, SHIP_TO). Create Site Use Validate and Commit – Check the return status and commit changes if successful. Validate and Commit Example: Create Customer in Oracle Apps R12 The following PL/SQL block demonstrates customer creation step by step. DECLARE
   -- Party
   l_party_rec          HZ_PARTY_V2PUB.party_rec_type;
   l_party_id           NUMBER;

   -- Customer Account
   l_cust_account_rec   HZ_CUST_ACCOUNT_V2PUB.cust_account_rec_type;
   l_cust_account_id    NUMBER;

   -- Customer Account Site
   l_cust_acct_site_rec HZ_CUST_ACCOUNT_V2PUB.cust_acct_site_rec_type;
   l_cust_acct_site_id  NUMBER;

   -- Customer Site Use
   l_cust_site_use_rec  HZ_CUST_ACCOUNT_V2PUB.cust_site_use_rec_type;
   l_cust_site_use_id   NUMBER;

   -- API return variables
   l_return_status      VARCHAR2(1);
   l_msg_count          NUMBER;
   l_msg_data           VARCHAR2(2000);
BEGIN
   -- Step 1: Create Party
   l_party_rec.party_type := 'ORGANIZATION';
   l_party_rec.party_name := 'XYZ TRADING COMPANY';

   HZ_PARTY_V2PUB.create_party (
       p_init_msg_list => FND_API.G_TRUE,
       p_party_rec     => l_party_rec,
       x_party_id      => l_party_id,
       x_return_status => l_return_status,
       x_msg_count     => l_msg_count,
       x_msg_data      => l_msg_data
   );

   IF l_return_status <> FND_API.G_RET_STS_SUCCESS THEN
      DBMS_OUTPUT.put_line('Party Creation Failed: ' || l_msg_data);
      RETURN;
   END IF;

   -- Step 2: Create Customer Account
   l_cust_account_rec.party_id := l_party_id;
   l_cust_account_rec.account_name := 'XYZ Trading Account';

   HZ_CUST_ACCOUNT_V2PUB.create_cust_account (
       p_init_msg_list   => FND_API.G_TRUE,
       p_cust_account_rec => l_cust_account_rec,
       x_cust_account_id => l_cust_account_id,
       x_return_status   => l_return_status,
       x_msg_count       => l_msg_count,
       x_msg_data        => l_msg_data
   );

   IF l_return_status <> FND_API.G_RET_STS_SUCCESS THEN
      DBMS_OUTPUT.put_line('Customer Account Creation Failed: ' || l_msg_data);
      RETURN;
   END IF;

   -- Step 3: Create Account Site
   l_cust_acct_site_rec.cust_account_id := l_cust_account_id;
   l_cust_acct_site_rec.party_site_id   := NULL; -- Can link to party site if exists
   l_cust_acct_site_rec.org_id          := 204; -- Operating Unit ID

   HZ_CUST_ACCOUNT_V2PUB.create_cust_acct_site (
       p_init_msg_list      => FND_API.G_TRUE,
       p_cust_acct_site_rec => l_cust_acct_site_rec,
       x_cust_acct_site_id  => l_cust_acct_site_id,
       x_return_status      => l_return_status,
       x_msg_count          => l_msg_count,
       x_msg_data           => l_msg_data
   );

   IF l_return_status <> FND_API.G_RET_STS_SUCCESS THEN
      DBMS_OUTPUT.put_line('Customer Account Site Creation Failed: ' || l_msg_data);
      RETURN;
   END IF;

   -- Step 4: Create Site Use (Billing/Shipping)
   l_cust_site_use_rec.cust_acct_site_id := l_cust_acct_site_id;
   l_cust_site_use_rec.site_use_code     := 'BILL_TO'; -- or SHIP_TO

   HZ_CUST_ACCOUNT_V2PUB.create_cust_site_use (
       p_init_msg_list     => FND_API.G_TRUE,
       p_cust_site_use_rec => l_cust_site_use_rec,
       x_cust_site_use_id  => l_cust_site_use_id,
       x_return_status     => l_return_status,
       x_msg_count         => l_msg_count,
       x_msg_data          => l_msg_data
   );

   IF l_return_status = FND_API.G_RET_STS_SUCCESS THEN
      DBMS_OUTPUT.put_line('Customer Created Successfully!');
      DBMS_OUTPUT.put_line('Party ID: ' || l_party_id);
      DBMS_OUTPUT.put_line('Account ID: ' || l_cust_account_id);
      DBMS_OUTPUT.put_line('Site ID: ' || l_cust_acct_site_id);
      DBMS_OUTPUT.put_line('Site Use ID: ' || l_cust_site_use_id);
      COMMIT;
   ELSE
      DBMS_OUTPUT.put_line('Customer Site Use Creation Failed: ' || l_msg_data);
      ROLLBACK;
   END IF;
END;
/ DECLARE
   -- Party
   l_party_rec          HZ_PARTY_V2PUB.party_rec_type;
   l_party_id           NUMBER;

   -- Customer Account
   l_cust_account_rec   HZ_CUST_ACCOUNT_V2PUB.cust_account_rec_type;
   l_cust_account_id    NUMBER;

   -- Customer Account Site
   l_cust_acct_site_rec HZ_CUST_ACCOUNT_V2PUB.cust_acct_site_rec_type;
   l_cust_acct_site_id  NUMBER;

   -- Customer Site Use
   l_cust_site_use_rec  HZ_CUST_ACCOUNT_V2PUB.cust_site_use_rec_type;
   l_cust_site_use_id   NUMBER;

   -- API return variables
   l_return_status      VARCHAR2(1);
   l_msg_count          NUMBER;
   l_msg_data           VARCHAR2(2000);
BEGIN
   -- Step 1: Create Party
   l_party_rec.party_type := 'ORGANIZATION';
   l_party_rec.party_name := 'XYZ TRADING COMPANY';

   HZ_PARTY_V2PUB.create_party (
       p_init_msg_list => FND_API.G_TRUE,
       p_party_rec     => l_party_rec,
       x_party_id      => l_party_id,
       x_return_status => l_return_status,
       x_msg_count     => l_msg_count,
       x_msg_data      => l_msg_data
   );

   IF l_return_status <> FND_API.G_RET_STS_SUCCESS THEN
      DBMS_OUTPUT.put_line('Party Creation Failed: ' || l_msg_data);
      RETURN;
   END IF;

   -- Step 2: Create Customer Account
   l_cust_account_rec.party_id := l_party_id;
   l_cust_account_rec.account_name := 'XYZ Trading Account';

   HZ_CUST_ACCOUNT_V2PUB.create_cust_account (
       p_init_msg_list   => FND_API.G_TRUE,
       p_cust_account_rec => l_cust_account_rec,
       x_cust_account_id => l_cust_account_id,
       x_return_status   => l_return_status,
       x_msg_count       => l_msg_count,
       x_msg_data        => l_msg_data
   );

   IF l_return_status <> FND_API.G_RET_STS_SUCCESS THEN
      DBMS_OUTPUT.put_line('Customer Account Creation Failed: ' || l_msg_data);
      RETURN;
   END IF;

   -- Step 3: Create Account Site
   l_cust_acct_site_rec.cust_account_id := l_cust_account_id;
   l_cust_acct_site_rec.party_site_id   := NULL; -- Can link to party site if exists
   l_cust_acct_site_rec.org_id          := 204; -- Operating Unit ID

   HZ_CUST_ACCOUNT_V2PUB.create_cust_acct_site (
       p_init_msg_list      => FND_API.G_TRUE,
       p_cust_acct_site_rec => l_cust_acct_site_rec,
       x_cust_acct_site_id  => l_cust_acct_site_id,
       x_return_status      => l_return_status,
       x_msg_count          => l_msg_count,
       x_msg_data           => l_msg_data
   );

   IF l_return_status <> FND_API.G_RET_STS_SUCCESS THEN
      DBMS_OUTPUT.put_line('Customer Account Site Creation Failed: ' || l_msg_data);
      RETURN;
   END IF;

   -- Step 4: Create Site Use (Billing/Shipping)
   l_cust_site_use_rec.cust_acct_site_id := l_cust_acct_site_id;
   l_cust_site_use_rec.site_use_code     := 'BILL_TO'; -- or SHIP_TO

   HZ_CUST_ACCOUNT_V2PUB.create_cust_site_use (
       p_init_msg_list     => FND_API.G_TRUE,
       p_cust_site_use_rec => l_cust_site_use_rec,
       x_cust_site_use_id  => l_cust_site_use_id,
       x_return_status     => l_return_status,
       x_msg_count         => l_msg_count,
       x_msg_data          => l_msg_data
   );

   IF l_return_status = FND_API.G_RET_STS_SUCCESS THEN
      DBMS_OUTPUT.put_line('Customer Created Successfully!');
      DBMS_OUTPUT.put_line('Party ID: ' || l_party_id);
      DBMS_OUTPUT.put_line('Account ID: ' || l_cust_account_id);
      DBMS_OUTPUT.put_line('Site ID: ' || l_cust_acct_site_id);
      DBMS_OUTPUT.put_line('Site Use ID: ' || l_cust_site_use_id);
      COMMIT;
   ELSE
      DBMS_OUTPUT.put_line('Customer Site Use Creation Failed: ' || l_msg_data);
      ROLLBACK;
   END IF;
END;
/ Best Practices for Using the Customer Creation API When using the customer creation API in Oracle Apps R12, keep these best practices in mind: Validate Input Data: Ensure mandatory fields like party name, account name, and site use code are provided.Handle Commit Carefully: Use explicit commits to avoid partial data creation.Capture Errors: Always log x_msg_data for debugging.Use Test Instances: Try APIs in test environments before moving to production.Build Wrappers: Consider creating wrapper programs for bulk customer creation. Validate Input Data: Ensure mandatory fields like party name, account name, and site use code are provided. Validate Input Data: Handle Commit Carefully: Use explicit commits to avoid partial data creation. Handle Commit Carefully: Capture Errors: Always log x_msg_data for debugging. Capture Errors: x_msg_data Use Test Instances: Try APIs in test environments before moving to production. Use Test Instances: Build Wrappers: Consider creating wrapper programs for bulk customer creation. Build Wrappers: Benefits of Automating Customer Creation Scalability: Onboard thousands of customers at once. Scalability: Onboard thousands of customers at once. Scalability: Data Quality: Enforces consistency and standardization. Data Quality: Enforces consistency and standardization. Data Quality: Integration Ready: Works with CRM, portals, and sales platforms. Integration Ready: Works with CRM, portals, and sales platforms. Integration Ready: Time Savings: Reduces manual entry workload for users. Time Savings: Reduces manual entry workload for users. Time Savings: Improved Efficiency: Automates complete customer lifecycle setup. Improved Efficiency: Automates complete customer lifecycle setup. Improved Efficiency: Conclusion Creating customers manually through Oracle Receivables is fine for a few records, but for large-scale operations, using APIs is far more efficient. The HZ_CUST_ACCOUNT_V2PUB package, along with HZ_PARTY_V2PUB, provides everything needed to automate customer creation, including parties, accounts, sites, and site uses. HZ_CUST_ACCOUNT_V2PUB HZ_CUST_ACCOUNT_V2PUB HZ_PARTY_V2PUB HZ_PARTY_V2PUB By following the example and steps outlined in this article, you now know how to create customer using API in Oracle Apps R12 in a structured and reliable way. This approach ensures accuracy, saves time, and integrates customer onboarding with broader business systems. how to create customer using API in Oracle Apps R12 The post How to Create Customer Using API in Oracle Apps R12 appeared first on Vinish.Dev. How to Create Customer Using API in Oracle Apps R12 Vinish.Dev

Walkthroughs, tutorials, guides, and tips. This story will teach you how to do something new or how to do something better.

This story contains AI-generated text. The author has used AI either for research, to generate outlines, or write the text itself. 

Automate Customer Creation in Oracle Apps R12 with This Simple API Trick

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

3 Steps to Creating Purchase Orders via API in Oracle R12

08/05/2018: Biggest Stories in the Cryptosphere

10 Best Online Courses to Learn Oracle and PL/SQL for Beginners

2019 Database Trends – SQL vs. NoSQL, Top Databases, Single vs. Multiple Database Use

4 Decentralized Oracle Platforms that Bridge Real-World Data to the Blockchain

3 Steps to Creating Purchase Orders via API in Oracle R12

08/05/2018: Biggest Stories in the Cryptosphere

10 Best Online Courses to Learn Oracle and PL/SQL for Beginners

2019 Database Trends – SQL vs. NoSQL, Top Databases, Single vs. Multiple Database Use

4 Decentralized Oracle Platforms that Bridge Real-World Data to the Blockchain

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps