EAP: NUM2 and NUM2_OTHER Fields Have Different Lengths in FSCM Compared to HCM (Doc ID 2785757.1)

Last updated on AUGUST 24, 2023

Applies to:

Symptoms

The NUM2 and NUM2_OTHER fields have different lengths in HCM and FSCM. In HCM, both fields have a field length of 6. However, in FSCM, both fields have a field length of 4.

When it comes to the Supplier, these fields are used in the Address for the countries of Spain, Netherlands and Belgium. NUM2 is used for "Door", and NUM2_OTHER is used for "Number".

Not using VENDOR_SYNC since experiencing issues with blanking out parts of the Supplier. So, using a custom sync process to update the Supplier Address.

If the NUM2 and NUM2_OTHER fields are populated with 6 characters on the HCM side, when using the custom sync process to update the Supplier Address from HCM to FSCM, these fields are truncated on the FSCM side since the NUM2 and NUM2_OTHER fields can only populate up to 4 characters.

Regardless if executing VENDOR_SYNC or a custom sync process, the field lengths of the NUM2 and NUM2_OTHER fields on the FSCM side should match the field lengths of the NUM2 and NUM2_OTHER fields on the HCM side.

STEPS
1. In Application Designer on the HCM side, display the fields of NUM2 and NUM2_OTHER
2. Notice that both have a length of 6
3. In Application Designer on the FSCM side, display the fields of NUM2 and NUM2_OTHER
4. Notice that both have a length of 4
5. If try to run a sync process (such as VENDOR_SYNC or custom sync) from HCM to FSCM to update the Supplier Address, and the NUM2 and NUM2_OTHER fields are populated with 6 characters on the HCM side, these fields are truncated on the FSCM side since the NUM2 and NUM2_OTHER fields can only populate up to 4 characters

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.