Once you create and test personalizations in
your test instance, you can move them to production instances. Personalizations
can be extracted by the loader on a per-function basis or per-form basis (that
is, each loader file will contain all of the personalizations for a single
function or form, respectively). Note that upon uploading, all prior
personalizations for that function are first deleted, and then the contents of
the loader file are inserted.
The loader syntax is as follows:
To download rules for a particular function:
FNDLOAD / 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct FND_FORM_CUSTOM_RULES function_name=
Note: this style is not recommended, as the personalizations that affect a particular function can now be a mix of function- and form-level rules.
To download rules for a particular form:
FNDLOAD/ 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lctFND_FORM_CUSTOM_RULES form_name=
To download all personalizations (all forms and functions):
FNDLOAD / 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct FND_FORM_CUSTOM_RULES
Upload:
FNDLOAD / 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct
The loader syntax is as follows:
To download rules for a particular function:
FNDLOAD / 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct FND_FORM_CUSTOM_RULES function_name=
Note: this style is not recommended, as the personalizations that affect a particular function can now be a mix of function- and form-level rules.
To download rules for a particular form:
FNDLOAD/ 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lctFND_FORM_CUSTOM_RULES form_name=
To download all personalizations (all forms and functions):
FNDLOAD / 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct FND_FORM_CUSTOM_RULES
Upload:
FNDLOAD / 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct
No comments:
Post a Comment