JA India Third Party Registration Upload creates and updates Oracle India Localization third party registrations for suppliers and customers from Excel: tax registration types and numbers such as GST, PAN, TAN, TIN and Service Tax with their effective dates, plus the reporting codes attached to a party registration. Existing registrations and reporting codes can be downloaded, changed and uploaded again.
When to use it
- Load GST, PAN, TAN or other registration numbers for many suppliers and customers at once, for example during a go-live or an operating unit rollout.
- Register a party at site level (with an operating unit and party site) or without a site.
- Set the assessable price list (non-TDS regimes) or the default TDS section (TDS regime) on many registrations.
- End-date registrations or reporting codes in bulk.
- Attach reporting codes to existing party registrations for India statutory reporting.
Before you start
- Oracle India Localization is installed and its tax setup is complete: regimes, registration types, reporting types and reporting codes. On an instance without the India Localization third party registration setup, Run stops with an “ORA-00942: table or view does not exist” error.
- The supplier or customer and its sites already exist. The upload adds registration data to existing parties; it does not create them.
- For a new party, upload its Registration rows first and its Reporting Code rows afterwards: a reporting code is attached to an existing party registration.
Step 1 – Set the parameters
Open JA India Third Party Registration Upload in Blitz Report. All parameters are optional and restrict which existing registrations and reporting codes are downloaded for editing:
| Parameter | Meaning |
|---|---|
| Operating Unit | Restricts the download to registrations of one operating unit. |
| Party Type | Supplier or Customer. The Party Name and Party Number lists depend on it. |
| Party Name / Party Number | Restrict the download to one supplier or customer. |
| Party Site Name | Restricts the download to one site of the selected party. |
| Regime Code | Restricts registrations by regime code (partial match, not case sensitive). |
| Registration Number | Restricts registrations by registration number (partial match, not case sensitive). |
Step 2 – Run to download the Excel file
Click Run. The Excel file downloads and opens with one row per registration line (Record Type Registration) and one row per reporting code (Record Type Reporting Code) of the selected parties. Add new rows below them, or below the header if nothing was downloaded.
Step 3 – Enter or change the data
On each new row choose the Record Type, then identify the party:
- Party Type – Supplier or Customer.
- Party Number – the supplier number or customer account number from the list; Party Name fills in from it. You can also pick the name, and the list shows the number next to it.
- Operating Unit and Party Site Name – for a site level registration select the operating unit and then the supplier site code or customer site number; the site list is limited to the operating unit. Leave both blank for a registration without a site. An operating unit without a site is rejected.
For a Registration row enter the Registration Regime Code, Registration Type and Registration Number, optionally a Secondary Registration Type and Secondary Registration Number, and either the Assessable Price List (non-TDS regimes) or the Default Tds Section (TDS regime). Registration Start Date defaults to 01-Jul-2017, the India GST start date; change it if needed and set a Registration End Date to end a registration.
For a Reporting Code row enter the Reporting Code Regime Code, the Reporting Code Type and a Reporting Code of that type. Reporting Code Start Date also defaults to 01-Jul-2017; Reporting Code End Date is optional.
On downloaded rows the identifying columns are locked. You can change the Assessable Price List, Default Tds Section, Registration End Date and Reporting Code End Date; a changed row is uploaded as an update.
Step 4 – Validate and Save
Click Validate and Save. It checks for missing required values and runs the upload’s validation (required registration or reporting code fields per Record Type, start dates not before 01-JUL-2017, end dates after start dates, TDS section versus price list), shows the problems in the Message column and saves the file. Correct any flagged rows before uploading.
Step 5 – Upload the file
In Blitz Report click Upload and select the saved file. This submits the upload request, which creates or updates the party registrations, registration lines and reporting codes.
Step 6 – Review the result report
When the request completes, a result report opens listing every uploaded row with its status and message, for example Registration created successfully or Reporting Code updated successfully. Correct rows with errors in the Excel file and upload them again.
What’s produced
- New or updated India Localization third party registrations: a party registration for the party (and site) is created when none exists, with one registration line per regime.
- New or updated reporting codes attached to the party registration.
- A result report listing every row with its status and message.
Common questions
Does this create the supplier or customer?
No. The supplier or customer and its sites must already exist; the upload only maintains their India Localization registrations.
What is the difference between the two Record Types?
A Registration row maintains a registration line (regime, registration type and number, dates). A Reporting Code row attaches a reporting code to the party registration of the same party and site. Upload the Registration rows of a new party first.
Can I change the regime or registration number of an existing registration?
No. These columns are locked on downloaded rows. End-date the existing line and add a new Registration row instead.
Can I add a second registration line for the same regime?
Not while one is active: a new line is rejected when the party and site already have an active line for that regime. End-date the existing line first, or update it.
Can I delete a registration with this upload?
No. It creates and updates only; use the end dates to end a registration or reporting code.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| ORA-00942: table or view does not exist | Shown on Run when the instance does not have the India Localization third party registration setup. | Use the upload on an instance with Oracle India Localization installed and set up. |
| Party Site Name is required when Operating Unit is entered | An operating unit was entered without a site. | Select a Party Site Name, or clear the Operating Unit for a registration without a site. |
| Registration Type is required / Registration Number is required / Registration Start Date is required | A Registration row is incomplete. | Fill in the missing column. |
| Registration Start Date cannot be earlier than 01-JUL-2017 | The start date is before the India GST start date. The same check applies to the Reporting Code Start Date. | Use a start date on or after 01-JUL-2017. |
| Registration End Date must be later than Registration Start Date | The end date is on or before the start date. The same check applies to reporting code dates. | Correct the dates. |
| Secondary Registration Number is required when Secondary Registration Type is entered | A secondary registration type has no number. | Enter the number or clear the type. |
| Assessable Price List must be blank for TDS regime / Default TDS Section must be blank for non-TDS regime | The wrong column is filled for the regime. | Use Default Tds Section for the TDS regime and Assessable Price List for other regimes. |
| Reporting Code Regime Code is required / Reporting Code Type is required / Reporting Code is required | A Reporting Code row is incomplete. | Fill in the missing column. |
| An active Registration Line already exists for this Party, Site and Regime combination. | A new Registration row duplicates an active registration line. | Update the existing line, or end-date it before adding a new one. |
| Party Registration not found. Create a Registration record first. | A new Reporting Code row is for a party and site without a party registration. | Upload a Registration row for that party and site first. |
| An active Reporting Code already exists for this Party Registration and Reporting Type combination. | The party registration already has an active reporting code of this type. | Update the downloaded reporting code row, or end-date it first. |