JA India Third Party Registration Upload
JA India Third Party Registration Upload creates and updates Oracle India Localization (GST) third-party tax registrations and their reporting codes for suppliers and customers from Excel – registration types and numbers such as GST, PAN, TAN, TIN and Service Tax, with effective dates.
When to use it
- Mass-load GST / PAN / TAN / TIN / Service Tax registrations for many suppliers and customers at once.
- Set up India Localization third-party registrations during a go-live or a new operating-unit rollout.
- Update effective dates or registration numbers on existing third-party registrations in bulk.
- Add secondary registration types/numbers to existing registrations.
- Assign assessable price lists (non-TDS regimes) or default TDS sections (TDS regime) across many parties.
- Attach reporting codes to existing third-party registrations for India statutory reporting.
Before you start
- Blitz Report is installed and Oracle India Localization is installed and set up (this upload is for R12 instances with India Localization).
- The supplier or customer already exists – this upload adds registration data to existing parties, it does not create them.
- For a Reporting Code row, a party registration must already exist (create the Registration first).
Step 1 – Set the parameters and download
In Blitz Report, open JA India Third Party Registration Upload and set the parameters to bring existing registrations into the template for editing, or leave them blank for an empty template:
| Parameter | Purpose |
|---|---|
| Operating Unit | Restrict to one operating unit. |
| Party Type / Party Name / Party Number / Party Site Name | Restrict to a supplier or customer (and site). |
| Regime Code / Registration Number | Restrict by regime or registration number. |
Run the upload to download and open the Excel file. Each row is automatically handled as a create or an update; existing rows carry a hidden identifier used to update them.
Step 2 – Enter the registrations
On each row choose the Record Type (Registration or Reporting Code), the Party Type, Party Number and Party Site Name. For a Registration, enter the Registration Regime Code, Registration Type and Registration Number with effective dates. For a Reporting Code, enter the Reporting Code Regime Code, Reporting Code Type and Reporting Code.
Step 3 – Validate and Save
Click Validate and Save. This checks for missing required values and runs the upload’s validation, then saves the file. Correct anything it flags before continuing.
Step 4 – Upload and view the result
Back in Blitz Report, click Upload and select your saved file. This submits the Blitz Upload request, which creates or updates each registration and reporting code. When it finishes, a result report opens showing each row as success or error.
What’s produced
- Created and updated India Localization third-party registrations and reporting codes.
- A result report listing every row with a status (success or error) and a message.
Common questions
Does this create the supplier or customer?
No. It only adds India Localization registration data to existing suppliers/customers – you must create the party first.
What’s the difference between the two Record Types?
Registration maintains the tax registration line (regime, type, number, dates). Reporting Code attaches a reporting code to an already-existing registration. Load Registration rows first, then Reporting Code rows.
Can I delete a registration with this upload?
No. It only creates and updates; there is no delete option.
When do I fill Assessable Price List vs Default TDS Section?
Use Default TDS Section for a TDS regime; use Assessable Price List for non-TDS regimes. The upload rejects the wrong combination.
Can I create a registration without a site?
Yes – leave Operating Unit and Party Site Name blank for an organization-independent (null-site) registration. If you enter an Operating Unit, you must also enter a Party Site Name.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| An active Registration Line already exists for this Party, Site and Regime | A Create row duplicates an existing active registration line. | Use an Update row on the existing line, or change the regime/site. |
| Party Registration not found – create a Registration record first | A Reporting Code row points at a party/site with no registration header yet. | Upload the Registration row(s) first, then the Reporting Code rows. |
| Assessable Price List must be blank for TDS regime / Default TDS Section must be blank for non-TDS regime | The wrong field is filled for the regime. | Use Default TDS Section for TDS, Assessable Price List for non-TDS. |
| Start Date cannot be earlier than 01-JUL-2017 | An effective start date before India GST go-live. | Use a start date on or after 01-JUL-2017. |
| Party Site Name is required when Operating Unit is entered | An operating unit was given without a site. | Enter a Party Site Name, or clear the Operating Unit for a null-site registration. |
select null action_, null status_, null message_, null modified_columns_, 'Registration' record_type, jprv.party_reg_id, jprlv.party_reg_line_id, to_number(null) reporting_association_id, jprv.operating_unit, jprv.party_class_name party_type, jprv.party_number, jprv.party_name, jprv.party_site_name, jprlv.regime_code registration_regime_code, jprlv.registration_type_name registration_type, jprlv.registration_number, jprlv.sec_registration_type_name secondary_registration_type, jprlv.secondary_registration_number, jprlv.assessable_price_list_name assessable_price_list, jprlv.default_section_name default_tds_section, jprlv.effective_from registration_start_date, jprlv.effective_to registration_end_date, to_char(null) reporting_code_regime_code, to_char(null) reporting_code_type, to_char(null) reporting_code, to_date(null) reporting_code_start_date, to_date(null) reporting_code_end_date from jai_party_regs_v jprv, jai_party_reg_lines_v jprlv where 1=1 and jprv.reg_class_code='THIRD_PARTY' and jprv.party_reg_id=jprlv.party_reg_id union all select null action_, null status_, null message_, null modified_columns_, 'Reporting Code' record_type, jprv.party_reg_id, to_number(null) party_reg_line_id, jrav.reporting_association_id, jprv.operating_unit, jprv.party_class_name party_type, jprv.party_number, jprv.party_name, jprv.party_site_name, to_char(null) registration_regime_code, to_char(null) registration_type, to_char(null) registration_number, to_char(null) secondary_registration_type, to_char(null) secondary_registration_number, to_char(null) assessable_price_list, to_char(null) default_tds_section, to_date(null) registration_start_date, to_date(null) registration_end_date, jrav.regime_code reporting_code_regime_code, jrav.reporting_type_name reporting_code_type, jrav.reporting_code, jrav.effective_from reporting_code_start_date, jrav.effective_to reporting_code_end_date from jai_party_regs_v jprv, jai_reporting_associations_v jrav where 1=1 and jprv.reg_class_code='THIRD_PARTY' and jprv.party_reg_id=jrav.entity_id and jrav.entity_code='THIRD_PARTY' order by party_type, party_number, record_type, party_reg_id, party_reg_line_id nulls last, reporting_association_id |
| Parameter Name | SQL text | Validation | |
|---|---|---|---|
| Operating Unit |
| LOV | |
| Party Type |
| LOV | |
| Party Name |
| LOV | |
| Party Number |
| LOV | |
| Party Site Name |
| LOV | |
| Regime Code |
| Char | |
| Registration Number |
| Char |