Webadi_ configuration Settings 2_ set interface Webadi Interface (case)

Webadi

This is the second and most critical step in building a new integrator!

Interface Name: write anyway, Oracle will generate a Interface code, and this is what we need, and what we need, Oracle does not let us see, but also add something ... The generated code should be integrator code + INTF1 or something like that.

Interface Type: mainly table and API Procedure. So when to use table, when to use procedure? Here is my personal opinion, for reference only:

1. If the validation is particularly simple (it is a single-field check), and the data on the template is to be entered in a table, use table.

2. If the validation is more complex (may include multi-line combination check, such as the order line amount is equal to the head amount, multi-field combination check, such as a vendor, some vendor site under the invoice of such currency can not have such , duplicate check, such as a certain asset, in the base table or interface already have, can not be used Tempate guide again and so on, because these checks to write Java class, I do not know how to write (hateful Oracle also no document). So you can only use procedure to do it.

3. If the data of the template is only used to pass to the standard API, to do some processing, do not have to enter a table, of course, do not use table, but with procedure.

Table name : name, this table needs to be registered in database, otherwise it will not be recognized.

Package Name: Needless to say, the name of the upload package you wrote

Procedure Name: Upload Procedure's name

API returns: Procedure/function outgoing parameters, generally selected FND message code, to receive Procedure raise out of error.

Apply a bit:

Attribute Name: is actually the field of the table or the name of the passed-in parameter of the procedure.

Prompt Left: this to change, the general format is "Invoice number", you can only be placed on the layout header on the field changes, because the field on the line only Prompt above, there is no left.

Data Type: inherited from table or procedure.

Enabled: If this option is not selected, the field can be displayed in the template and can be filled in, but the data will not participate in the upload. That is, this field is completely useless (for some fields that do not need to be filled in).

Displayed: If this option is not selected, you will not see this item when you define layout. You can't see it in the template. Of course, even if you choose this, but the layout is not selected, it is not visible.

Default type/default value: used to set the value of the field, in the 11i I generally defined in the layout, but R12 seems to be mainly defined here, layout of default instead of, And I am in the layout of the definition seems to be old problems, I do not know whether it is a bug, or other reasons.

Environment Parameters: Oauser.id/sysdate/database commonly used, and some other sob, such as Sob.chartofaccountsid, Sob.periodsetname, Sob.setofbooksid and so on, I do not know whether it can be used, It's not tested.

Constant: This is the simplest, just write a thing and go in.

sql: This is also simple, write a SQL done, the results of multiple lines, take the first line. SQL can contain $env$.userid, $env $.appid, $env $.respid and other environment variables, as well as $profiles$.default_org_id, such as the profile options.

Profile option: literally, it's used to take the value of an Option in a configuration file, but I did it, didn't succeed, I didn't know it was a bug or something.

Lookups: do not know what to do, the first two days have no intention to see there is a standard integrator contains multiple interface, and interface between the connection seems to use this ... Because this item is called Tablelookup in the backstage ... Many interface integrator still do not know how to do, pending research.

Excel Formula: This does not need to select the default type, directly enter the formula in default value, the format is as follows: =r[]c[]* r[]c[], such as =rc[-1]*rc[-2], that The value of the field is the product of the left two columns.

Sequence: This requires a background modification table, default type is Sequence_each_row, default value is Sequence name, if not under the apps, you need to create synonyms under apps

Attribute Type: Real indicates that this field is a real table field or a process parameter, and custom is our additional fields, generally used to make a rank (such as a lov display is DESC, the ID is stored, this desc is generally placed in this joins) or read-only display items, For example, display the current database information.

You can modify some of the properties of a field by following the update at the point.

Data Type:No need to change, inherited from table or procedure
Length:It is found that this is not, because this is based on the procedure interface, and for procedure, all incoming parameters are not length, and if based on table, there will be length. The result of no length is that Excel cannot do a field width check, and you need to write such a statement in procedure:
If Length (p_vendor_name) >
Raise_application_error ( -20001, ' Length exceeds Max chars ');
End If;
This significantly increases the amount of development, so for procedure interface, we can set the length of the field by directly modifying the background table.
Attribute Type:No modifications required
Required:This is important, the setting field is required, if you do not lose on the template, Excel check will error, so you do not have to write such statements in the procedure:
If p_vendor_name is null then
Raise_application_error ( -20001, ' You had to enter a Vendor name ');
End If;

Enabled for Mapping:Set whether the field can be built mapping, when your integrator contains content, this useful, in general, to display in the layout of the field to choose, other optional.

Available for Summary:This does not know, literally whether it is allowed to summarize. Not measured.
Not Null: This seems to be the same as the required function.
Read only: Sets a field that is read-only and generally applies to the display field of the custom type. Or a field with a default value that does not require user modification.

The following is the building validation section, where you can build table LOV, date LOV, KFF/DFF LOV, and Java type LOV.


The last part is set prompt above, for the field on line, this item should be written. User hint It is best to write, the required fields are generally *text, *date, *number such, not required to fill the * go. There are generally lov, such as List-text or List-text.

http://blog.itpub.net/10359218/viewspace-734471/

Webadi_ configuration Settings 2_ set interface Webadi Interface (case)