| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| mnIdentifierShortItem | ITM | MATH_NUMERIC | OPT | NONE |
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item
numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and
so forth. The item numbers are as follows:
o Item Number (short) - An eight-digit, computer-assigned item number
o 2nd Item Number - The
25-digit, free-form, user defined alphanumeric item number
o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item
number |
| mnAddressNumberShipTo | SHAN | MATH_NUMERIC | OPT | NONE |
The address number of the location to which you want to ship this order. The address book provides default values for customer address,
including street, city, state, zip code, and country. |
| szCostCenter | MCU | char | OPT | NONE |
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
might be a warehouse location, job, project, work center, branch, or plant.
You can assign a business unit to a document, entity, or person for
purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by
business unit to track equipment by responsible department.
Business unit security might prevent you from viewing information about business units
for which you have no authority.
|
| mnAddressNumber | AN8 | MATH_NUMERIC | OPT | NONE |
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or
location.
|
| mnCodeTransactionNature | BNOP | MATH_NUMERIC | OPT | NONE |
A three-character code that for tax purposes, identifies a type of transaction. To enter valid values for the Transaction Nature code, use the
following convention: X.YY X defines the origin of the transaction (inbound or outbound). Valid values for X are:
1
Inbound, inside the
state.
2
Inbound, other states.
3
Inbound, import.
5
Outbound, inside state.
6
Outbound, other states.
7
Outbound, export.
YY defines the transaction as a
whole, such as a sales transaction.
Examples of Transaction Nature codes:
511 In-state sale
611 Out-of-state sale |
| szSuffixTransactionNature | BSOP | char | OPT | NONE |
Complete this two-character field in conjunction with the Transaction Nature code to identify the complementary implications of a type of
transaction. For example, the suffix might indicate that a certain type of transaction represents a inventory change, or that a transaction is eligible
for a certain type of tax.
Valid values might include:
01
Bonus
02
Demo
03
Sample
04
Return merchandise
05
Back order
06
Donation
Examples of
Transaction Nature codes with suffixes:
511 01
In-state sale, bonus
511 05
In-state sale, back order |
| cFlagICMSTaxSubstitutionMarkUp | BIST | char | OPT | NONE |
A code that specifies whether a client or product is subject to tax substitution. Valid values are:
Y
Use list price.
Z
Use net price.
N
No.
|
| szCodePurchaseUse | BCFC | char | OPT | NONE |
A code that identifies the purpose for which the merchandise was purchased. You define purchase use codes in the Purchase Use UDC
table (76/PU). When you define purchase use codes, use the special handling code to specify the following tax information:
For ICMS
tax:
0
ICMS tax is nonrecoverable
1
ICMS tax is 100 percent recoverable
For IPI tax:
0
IPI tax is nonrecoverable
1
IPI tax is 50 or 100 percent recoverable,
depending on the status of the ship-to and ship-from taxpayer |