This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Documentation

Welcome to connectSpec (OAGIS) 10.11.2 documentation produced on 2024-08-19!

OAGi welcomes your feedback. It will make a difference!

Scenarios

BODs (messages)

Verbs

Nouns

Components

1 - Scenarios

By Scenario Number

• 1 • 2 • 3 • 4 • 5 • 6 • 7 • 8 • 9 • 10 • 11 • 12 • 13 • 14 • 15 • 16 • 17 • 18 • 19 • 20 • 21 • 22 • 23 • 24 • 25 • 26 • 27 • 28 • 29 • 30 • 31 • 32 • 33 • 34 • 35 • 36 • 37 • 38 • 39 • 40 • 41 • 42 • 43 • 44 • 45 • 46 • 47 • 48 • 49 • 50 • 51 • 52 • 53 • 54 • 55 • 56 • 57 • 58 • 59 • 60 • 61 • 62 • 63 • 64 • 64 • 64 • 65 • 66 • 67 • 68 • 69 • 70 • 71 • 72 • 73 • 74 • 78 • 79 • 80 • 81 • 82 • 83 • 83 • 84 • 84 • 85 • 86 • 87 • 88 • 89 • 89 • 90 • 91 • 92 • 93 • 94 • 94 • 95 • 95 • 96 • 96 • 97 • 97 • 98 • 98 •

By Category

Customer Service

Engineering

ERP

Financial

Generic Information

Human Resources

Invoicing

Life Cycle Analysis

Life Cycle Cost Analysis

Logistics

Manufacturing

Master Data Management

Mid-Market

Order

Process Specialization

Procurement

Product Support Management

Project Management

Purchasing

Quality

RESTFUL Data Acquisition

Sales Process

Service Request

Shop Floor Manufacturing

Supply Chain Integration

Warehouse

Work Breakdown Structure

Alphabetical

Feedback

OAGi and its members welcome your feedback.

connectSpec (OAGIS) Version 10.11.2

2 - BODs

A

B

C

D

E

F

G

H

I

J

L

M

O

P

Q

R

S

T

U

W

Feedback

OAGi and its members welcome your feedback.

OAGIS Version 10.11.2

3 - Verbs

  1. Acknowledge
  2. Cancel
  3. Get
  4. Process
  5. Cancel Acknowledge
  6. Sync
  7. Confirm
  8. Show
  9. Change
  10. Notify
  11. Change Acknowledge
  12. Sync Response
  13. Load Response
  14. Post Acknowledge
  15. Load
  16. Post

Feedback

OAGi and its members welcome your feedback.

OAGIS Version 10.11.2

4 - Nouns

Feedback

OAGi and its members welcome your feedback.

OAGIS Version 10.11.2

5 - Component Index

A

B

C

D

E

F

G

H

I

J

K

L

M

N

O

P

Q

R

S

T

U

V

W

X

Y

Z

Feedback

OAGi and its members welcome your feedback.

UUID: |>Uuid<|

connectSpec (OAGIS) Version 10.11.2

6 - Absence Type Code

This describes the type of absence a worker is reporting in a time and attendance collection process

Data Type Description

This data type is based on the following data type primitives. Schema expressions and implementation refinements may further restrict the data type.

  • NormalizedString
  • String
  • Token

Supplementary Components

Type Code

Required: No

List Identifier

Required: No

List Agency Identifier

Required: No

List Version Identifier

Required: No

Feedback

OAGi and its members welcome your feedback.

UUID: 80203ad4a0ca4894885987a92c48ef5f

connectSpec (OAGIS) Version 10.11.2

7 - Accept By Date Time

Date by which the vendor is expected to accept the PO

Data Type Description

This data type is based on the following data type primitives. Schema expressions and implementation refinements may further restrict the data type.

  • TimePoint

Supplementary Components

Type Code

Required: No

Feedback

OAGi and its members welcome your feedback.

UUID: 9e296d05f0044d06ad2b4f564cb5bad1

connectSpec (OAGIS) Version 10.11.2

8 - Acceptable Name Value Range

A representation of some limits usually expressed as a high and low limit

Child Components

Type Code 0..1
Upper Limit 0..1
Lower Limit 0..1

UML Class Model

The following link opens the SVG image in a separate browser tab.
You can save the file locally and use it, for example, in PowerPoint.
SVG File 
@startuml AcceptableNameValueRange

class AcceptableNameValueRange {
    String [[/docs/type-code TypeCode]]
    String [[/docs/upper-limit UpperLimit]]
    String [[/docs/lower-limit LowerLimit]]
}


hide circle
@enduml

Where Used

Following is a list of components that have Acceptable Name Value Range as a child component.

Feedback

OAGi and its members welcome your feedback.

UUID: 8d9fc01773c34542b015875134f35ae0

connectSpec (OAGIS) Version 10.11.2

9 - Acceptable Value

The value that would represents a satisfactory outcome

Data Type Description

This data type is based on the following data type primitives. Schema expressions and implementation refinements may further restrict the data type.

  • Decimal
  • Double
  • Float
  • Integer
  • NormalizedString
  • String
  • Token

Supplementary Components

Name Name

Required: Yes

Type Code

Required: No

Unit Code

Required: No

Unit Code List Version Identifier

Required: No

Feedback

OAGi and its members welcome your feedback.

UUID: 8481f83d71d14f10b59d46027d363265

connectSpec (OAGIS) Version 10.11.2

10 - Accepted Indicator

Indicates whether the associated entity has been accepted or not.

Data Type Description

This data type is based on the following data type primitives. Schema expressions and implementation refinements may further restrict the data type.

  • Boolean

Supplementary Components

Type Code

Required: No

Feedback

OAGi and its members welcome your feedback.

UUID: 60de144430d049a094fd963109e033d6

connectSpec (OAGIS) Version 10.11.2

11 - Accepted Quantity

Indicates the quantity accepted.

Data Type Description

This data type is based on the following data type primitives. Schema expressions and implementation refinements may further restrict the data type.

  • Decimal
  • Double
  • Float
  • Integer

Supplementary Components

Type Code

Required: No

Unit Code

Required: No

Feedback

OAGi and its members welcome your feedback.

UUID: 1c8b201781564779b04053b0886b313b

connectSpec (OAGIS) Version 10.11.2

12 - Access

The text that permits access to the electronic network of the associated communication number such as telephone network, for example 9, *70.

Data Type Description

This data type is based on the following data type primitives. Schema expressions and implementation refinements may further restrict the data type.

  • NormalizedString
  • String
  • Token

Supplementary Components

Type Code

Required: No

Language Code

Required: No

Feedback

OAGi and its members welcome your feedback.

UUID: 07ae3b827ec04814a6c9cfb3c51a7a5a

connectSpec (OAGIS) Version 10.11.2

13 - Access Control

Access Control List to indicate what application / functional components a user /role has access to.

Child Components

Type Code 0..1
Action Code 0..1
Identifier 0..∞
UUID 0..1
Source Identifier 0..1
Party Identifier 0..1
Related Identifier 0..∞
Revision Identifier 0..1
Variation Identifier 0..1
Document Identifier Set 0..∞
Language Code 0..1
Last Modification Date Time 0..1
Document Date Time 0..1
Description 0..∞
Note 0..∞
Document Reference 0..∞
Attachment 0..∞
Security Classification 0..∞
Metadata Reference 0..∞
Name 0..∞
Control Code Type 0..1
Prevent Indicator 0..1
Detect Indicator 0..1
Approval Status 0..1
Control Component 0..∞
Control Objective Category 0..1
Control Assertion 0..1
Access Request Party 0..∞
Extension 1..1

UML Class Model

The following link opens the SVG image in a separate browser tab.
You can save the file locally and use it, for example, in PowerPoint.
SVG File 
@startuml AccessControl

class AccessControl {
    String [[/docs/type-code TypeCode]]
    CodeList [[/docs/action-code ActionCode]]
    String [[/docs/identifier Identifier]]
    String [[/docs/uuid UUID]]
    String [[/docs/source-identifier SourceIdentifier]]
    String [[/docs/party-identifier PartyIdentifier]]
    String [[/docs/revision-identifier RevisionIdentifier]]
    String [[/docs/variation-identifier VariationIdentifier]]
    String [[/docs/language-code LanguageCode]]
    TimePoint [[/docs/last-modification-date-time LastModificationDateTime]]
    TimePoint [[/docs/document-date-time DocumentDateTime]]
    String [[/docs/description Description]]
    String [[/docs/note Note]]
    String [[/docs/name Name]]
    CodeList [[/docs/control-code-type ControlCodeType]]
    Boolean [[/docs/prevent-indicator PreventIndicator]]
    Boolean [[/docs/detect-indicator DetectIndicator]]
    CodeList [[/docs/control-component ControlComponent]]
    CodeList [[/docs/control-objective-category ControlObjectiveCategory]]
    CodeList [[/docs/control-assertion ControlAssertion]]
}

class RelatedIdentifier {
    [[/docs/related-identifier details]]→
}

class DocumentIdentifierSet {
    [[/docs/document-identifier-set details]]→
}

class DocumentReference {
    [[/docs/document-reference details]]→
}

class Attachment {
    [[/docs/attachment details]]→
}

class SecurityClassification {
    [[/docs/security-classification details]]→
}

class MetadataReference {
    [[/docs/metadata-reference details]]→
}

class ApprovalStatus {
    [[/docs/approval-status details]]→
}

class AccessRequestParty {
    [[/docs/access-request-party details]]→
}

AccessControl o-d- "0...∞" RelatedIdentifier
AccessControl o-r- "0...∞" DocumentIdentifierSet
AccessControl o-u- "0...∞" DocumentReference
AccessControl o-l- "0...∞" Attachment
AccessControl o-d- "0...∞" SecurityClassification
AccessControl o-u- "0...∞" MetadataReference
AccessControl o-d- "0...1" ApprovalStatus
AccessControl o-u- "0...∞" AccessRequestParty

hide circle
@enduml

Where Used

Following is a list of components that have Access Control as a child component.

Feedback

OAGi and its members welcome your feedback.

UUID: d1df4b7e92384c96a37529d541b64c29

connectSpec (OAGIS) Version 10.11.2

14 - Access Request Party

Party who to request Access to a software resource or dataset.

Child Components

Type Code 0..1
Role 0..1
Action Code 0..1
Identifier 0..∞
Name 0..∞
Account Identifier 0..∞
URI 0..∞
Party Identifier Set 0..∞
Tax Identifier Set 0..∞
Tax Identifier 0..∞
DUNSID 0..∞
CAGEID 0..1
DODAACID 0..1
BICID 0..1
SCACID 0..1
CCRID 0..1
Government Issued Party Identifier 0..∞
Language Code 0..1
Signature 0..1
Description 0..∞
Note 0..∞
Location 0..∞
Contact 0..∞
Industry Classification Scheme 0..∞
Security Classification 0..∞
Classification 0..∞
Enterprise Unit 0..∞
Distribution Channel 0..∞
Extension 1..1

UML Class Model

The following link opens the SVG image in a separate browser tab.
You can save the file locally and use it, for example, in PowerPoint.
SVG File 
@startuml AccessRequestParty

class AccessRequestParty {
    String [[/docs/type-code TypeCode]]
    String [[/docs/role Role]]
    CodeList [[/docs/action-code ActionCode]]
    String [[/docs/identifier Identifier]]
    String [[/docs/name Name]]
    String [[/docs/account-identifier AccountIdentifier]]
    String [[/docs/uri URI]]
    String [[/docs/tax-identifier TaxIdentifier]]
    String [[/docs/dunsid DUNSID]]
    String [[/docs/cageid CAGEID]]
    String [[/docs/dodaacid DODAACID]]
    String [[/docs/bicid BICID]]
    String [[/docs/scacid SCACID]]
    String [[/docs/ccrid CCRID]]
    String [[/docs/government-issued-party-identifier GovernmentIssuedPartyIdentifier]]
    String [[/docs/language-code LanguageCode]]
    String [[/docs/description Description]]
    String [[/docs/note Note]]
}

class PartyIdentifierSet {
    [[/docs/party-identifier-set details]]→
}

class TaxIdentifierSet {
    [[/docs/tax-identifier-set details]]→
}

class Signature {
    [[/docs/signature details]]→
}

class Location {
    [[/docs/location details]]→
}

class Contact {
    [[/docs/contact details]]→
}

class IndustryClassificationScheme {
    [[/docs/industry-classification-scheme details]]→
}

class SecurityClassification {
    [[/docs/security-classification details]]→
}

class Classification {
    [[/docs/classification details]]→
}

class EnterpriseUnit {
    [[/docs/enterprise-unit details]]→
}

class DistributionChannel {
    [[/docs/distribution-channel details]]→
}

AccessRequestParty o-d- "0...∞" PartyIdentifierSet
AccessRequestParty o-r- "0...∞" TaxIdentifierSet
AccessRequestParty o-u- "0...1" Signature
AccessRequestParty o-l- "0...∞" Location
AccessRequestParty o-d- "0...∞" Contact
AccessRequestParty o-u- "0...∞" IndustryClassificationScheme
AccessRequestParty o-d- "0...∞" SecurityClassification
AccessRequestParty o-u- "0...∞" Classification
AccessRequestParty o-d- "0...∞" EnterpriseUnit
AccessRequestParty o-u- "0...∞" DistributionChannel

hide circle
@enduml

Where Used

Following is a list of components that have Access Request Party as a child component.

Feedback

OAGi and its members welcome your feedback.

UUID: cdb23ef32b5843a9b9d1a93a71a5a43f

connectSpec (OAGIS) Version 10.11.2

15 - Account Identifier

Identifier of the account

Data Type Description

This data type is based on the following data type primitives. Schema expressions and implementation refinements may further restrict the data type.

  • NormalizedString
  • String
  • Token
  • Integer

Supplementary Components

Type Code

Required: No

Scheme Identifier

Required: No

Scheme Version Identifier

Required: No

Scheme Agency Identifier

Required: No

Feedback

OAGi and its members welcome your feedback.

UUID: b57bb6335bb34f869d2c08082bf25846

connectSpec (OAGIS) Version 10.11.2

16 - Account Identifiers

Associated account of the associated entity.

Child Components

Identifier 1..∞

UML Class Model

The following link opens the SVG image in a separate browser tab.
You can save the file locally and use it, for example, in PowerPoint.
SVG File 
@startuml AccountIdentifiers

class AccountIdentifiers {
    String [[/docs/identifier Identifier]]
}


hide circle
@enduml

Where Used

Following is a list of components that have Account Identifiers as a child component.

Feedback

OAGi and its members welcome your feedback.

UUID: 2ed543b96bd94b60ab0f0396cbadb319

connectSpec (OAGIS) Version 10.11.2

17 - Account Name

Data Type Description

This data type is based on the following data type primitives. Schema expressions and implementation refinements may further restrict the data type.

  • NormalizedString
  • String
  • Token

Supplementary Components

Type Code

Required: No

Sequence Number

Required: No

Language Code

Required: No

Feedback

OAGi and its members welcome your feedback.

UUID: d0018ac1409147558d51219e04234a83

connectSpec (OAGIS) Version 10.11.2

18 - Account Type Code

Type of UserAccount.

Data Type Description

This data type is based on the following data type primitives. Schema expressions and implementation refinements may further restrict the data type.

  • NormalizedString
  • String
  • Token

Supplementary Components

Type Code

Required: No

List Identifier

Required: No

List Agency Identifier

Required: No

List Version Identifier

Required: No

Feedback

OAGi and its members welcome your feedback.

UUID: a616e3240dc448eab9e3211fa88cfaa3

connectSpec (OAGIS) Version 10.11.2

19 - Accounting Period

A period used for accounting period.

Child Components

Type Code 0..1
Action Code 0..1
Identifier 0..∞
UUID 0..1
Source Identifier 0..1
Party Identifier 0..1
Identifier Set 0..∞
Related Identifier 0..∞
Period Identifier 0..1
Post Date Time 0..1
Year 0..1
Name 0..1
Effective Time Period 0..1
Extension 1..1

UML Class Model

The following link opens the SVG image in a separate browser tab.
You can save the file locally and use it, for example, in PowerPoint.
SVG File 
@startuml AccountingPeriod

class AccountingPeriod {
    String [[/docs/type-code TypeCode]]
    CodeList [[/docs/action-code ActionCode]]
    String [[/docs/identifier Identifier]]
    String [[/docs/uuid UUID]]
    String [[/docs/source-identifier SourceIdentifier]]
    String [[/docs/party-identifier PartyIdentifier]]
    String [[/docs/period-identifier PeriodIdentifier]]
    TimePoint [[/docs/post-date-time PostDateTime]]
    TimePoint [[/docs/year Year]]
    String [[/docs/name Name]]
}

class IdentifierSet {
    [[/docs/identifier-set details]]→
}

class RelatedIdentifier {
    [[/docs/related-identifier details]]→
}

class EffectiveTimePeriod {
    [[/docs/effective-time-period details]]→
}

AccountingPeriod o-d- "0...∞" IdentifierSet
AccountingPeriod o-r- "0...∞" RelatedIdentifier
AccountingPeriod o-u- "0...1" EffectiveTimePeriod

hide circle
@enduml

Where Used

Following is a list of components that have Accounting Period as a child component.

Feedback

OAGi and its members welcome your feedback.

UUID: 57858d0342e54481940d038c4580792f

connectSpec (OAGIS) Version 10.11.2

20 - Accrued Amount

Costs incurred against this project activity are recorded in the AccruedAmount for the Activity.

Data Type Description

This data type is based on the following data type primitives. Schema expressions and implementation refinements may further restrict the data type.

  • Decimal
  • Double
  • Float
  • Integer

Supplementary Components

Type Code

Required: No

Currency Code

Required: No

Feedback

OAGi and its members welcome your feedback.

UUID: 5f8701cdd08a46058c90dfffa81e20c8

connectSpec (OAGIS) Version 10.11.2

21 - Accumulative Received Quantity

Data Type Description

This data type is based on the following data type primitives. Schema expressions and implementation refinements may further restrict the data type.

  • Decimal
  • Double
  • Float
  • Integer

Supplementary Components

Type Code

Required: No

Unit Code

Required: No

Feedback

OAGi and its members welcome your feedback.

UUID: 223a8853e883420da4e88965d78616bd

connectSpec (OAGIS) Version 10.11.2

22 - Verb: Acknowledge

The Acknowledge verb is used to acknowledge the application receipt of a Process request. This function conveys the result of the original request. An example of this is Acknowledge PO, where a Process PO has been issued and the corresponding business application acknowledges the receipt of the PO and responds with an acceptance or a counter offer.

Child Components

Original Application Area 0..1
Response Criteria 0..∞

Feedback

OAGi and its members welcome your feedback.

UUID: d9589936aace44f5bd890ec462888263

OAGIS Version 10.11.2

23 - BOD: Acknowledge Allocate Resource

The AcknowledgeAllocateResource may be used to obtain limited information Acknowledgeing about documents that match certain selection criteria in a GetAcknowledgeAllocateResource.

Additional information about a specific AllocateResource may be obtained through ShowAllocateResource by using the Acknowledgeing information to populate a GetAllocateResource request.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Allocate Resource 1..∞

Scenarios in which Acknowledge Allocate Resource is used

Feedback

OAGi and its members welcome your feedback.

UUID: 0a3753ce606a46128b365c400f895451

OAGIS Version 10.11.2

24 - BOD: Acknowledge Batch Certificate Of Analysis

The purpose of the AcknowledgeBatchCertificateOfAnalysis Business Object Document is to acknowledge receipt of the Purchase Order and to reflect any changes. Commonly, the acknowledgment is generated by an order management application and transmitted to a purchasing or procurement application.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Batch Certificate Of Analysis 1..∞

Scenarios in which Acknowledge Batch Certificate Of Analysis is used

Feedback

OAGi and its members welcome your feedback.

UUID: f942ac6bb54b48d3a4ec5ee2f06b9b1e

OAGIS Version 10.11.2

25 - BOD: Acknowledge BOM

The purpose of the SynBOM is to communicate to a business application module or system the need to initiate the creation of a Bill of Material structure.

This BOD may be necessary to address the Make to Order, Assemble to Order, or Mixed Mode business ordering scenarios in a Order Management to Manufacturing application integration scenario.

There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to communicate the requirement to Acknowledgehronize a Bill of Material.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      BOM 1..∞

Scenarios in which Acknowledge BOM is used

Feedback

OAGi and its members welcome your feedback.

UUID: d33e764ca8a34be982ddc2c03297f525

OAGIS Version 10.11.2

26 - BOD: Acknowledge Carrier Route

The purpose of the AcknowledgeCarrierRoute is to enable an application to provide Carrier Route information from another business application module. The AcknowledgeCarrierRoute is typiically provided in a publish/subscribe or broadcast environment. Where the sending system is the master application of the information being provided, where the information is sent to other business applications that need to know the information.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Carrier Route 1..∞

Scenarios in which Acknowledge Carrier Route is used

Feedback

OAGi and its members welcome your feedback.

UUID: cdede32de16d45b8bfb3de3697468ada

OAGIS Version 10.11.2

27 - BOD: Acknowledge Catalog

AcknowledgeCatalog is used to Acknowledgehronize catalog information across systems. The Acknowledge indicates that the send of the AcknowledgeCatalog is the owner of the information being passed, additionally it is understood that the receiver of the AcknowledgeCatalog is a sub-system that must accept the data as provided by the owne of the information.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Catalog 1..∞

Scenarios in which Acknowledge Catalog is used

Feedback

OAGi and its members welcome your feedback.

UUID: 5ebb4622603242d6a435185fed697ae8

OAGIS Version 10.11.2

28 - BOD: Acknowledge Chart Of Accounts

The purpose of the AcknowledgeChartOfAccounts is to supply ChartOfAccounts information to another business application module.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Chart Of Accounts 1..∞

Scenarios in which Acknowledge Chart Of Accounts is used

Feedback

OAGi and its members welcome your feedback.

UUID: 5537b5c902704ae38e1119dc19fbbf26

OAGIS Version 10.11.2

29 - Acknowledge Code

Data Type Description

This data type has the following code list values specified for it:

  • Always
  • OnError
  • OnModification
  • OnRejection
  • Never

Feedback

OAGi and its members welcome your feedback.

UUID: 4555176bbc11409195827baed0f42bd8

connectSpec (OAGIS) Version 10.11.2

30 - BOD: Acknowledge Code List

The purpose of the AcknowledgeCodeList is to supply a CodeList to another business application module.

This BOD addresses the need for applications to exchange item-independent alternative UOM information beyond the stocking UOM. See the Item UOM Integration Scenario for more detailed information.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Code List 1..∞

Scenarios in which Acknowledge Code List is used

Feedback

OAGi and its members welcome your feedback.

UUID: 565fd292a0ed4f7e8d5ae9630bcf5ba4

OAGIS Version 10.11.2

31 - BOD: Acknowledge Commercial Invoice

The purpose of the AcknowledgeCommercialInvoice Business Object Document is to acknowledge receipt of the CommercialInvoice

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Commercial Invoice 1..∞

Scenarios in which Acknowledge Commercial Invoice is used

Feedback

OAGi and its members welcome your feedback.

UUID: c5b73226d69a4cb3a50194a7b635859e

OAGIS Version 10.11.2

32 - BOD: Acknowledge Configuration

The purpose of the AcknowledgeConfiguration is to enable an application to provide Configuration information from one business application to another business application. The AcknowledgeConfiguration is provided in response to the ProcessConfiguration in order to communicate the results of processing.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Configuration 1..∞

Scenarios in which Acknowledge Configuration is used

Feedback

OAGi and its members welcome your feedback.

UUID: e94f69197a704a4f90b966c46edbb022

OAGIS Version 10.11.2

33 - BOD: Acknowledge Confirm WIP

The purpose of the AcknowledgeConfirmWIP is to respond to a request for the data necessary to perform a confirmation of the movement of WIP (Work in Progress).

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Confirm WIP 1..∞

Scenarios in which Acknowledge Confirm WIP is used

Feedback

OAGi and its members welcome your feedback.

UUID: 6e6dd70d522549e4b9abf108ec8f7b0d

OAGIS Version 10.11.2

34 - BOD: Acknowledge Contract

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Contract 1..∞

Scenarios in which Acknowledge Contract is used

Feedback

OAGi and its members welcome your feedback.

UUID: c9ae66dea9cd4747a2fbf862deb067c4

OAGIS Version 10.11.2

35 - BOD: Acknowledge Corrective Action

The purpose of the AcknowledgeCorrectiveAction is to communicate to a business application module or system the need to initiate the creation of a CorrectiveAction structure.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Corrective Action 1..∞

Scenarios in which Acknowledge Corrective Action is used

Feedback

OAGi and its members welcome your feedback.

UUID: 3f8c7ca8d3a7478b8d61a9d781f4bcd2

OAGIS Version 10.11.2

36 - BOD: Acknowledge Corrective Action Plan

The purpose of the AcknowledgeCorrectiveActionPlan is to communicate to a business application module or system the need to initiate the creation of a CorrectiveActionPlan structure.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Corrective Action Plan 1..∞

Scenarios in which Acknowledge Corrective Action Plan is used

Feedback

OAGi and its members welcome your feedback.

UUID: fc452f3777e44914964c15a3086b0671

OAGIS Version 10.11.2

37 - BOD: Acknowledge Corrective Action Request

The purpose of the AcknowledgeCorrectiveActionRequest is to communicate to a business application module or system the need to initiate the creation of a CorrectiveActionRequest structure.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Corrective Action Request 1..∞

Scenarios in which Acknowledge Corrective Action Request is used

Feedback

OAGi and its members welcome your feedback.

UUID: f8765f08dd1d4489937f0bf28b0659b7

OAGIS Version 10.11.2

38 - BOD: Acknowledge Credit

The purpose of the AcknowledgeCredit is for the order management application to request credit data for a trading partner from the credit management function. The AcknowledgeCredit does not imply any update, it is only an inquiry function. The ShowCredit discussed in the next chapter will be the response back to the order management application.

Discussed in a later chapter is the UpdateCredit. The UpdateCredit may be used in both directions between the order management and the accounts receivable application. Its purpose is to keep order, shipment and open item amounts current. Finally, the ChangeCreditStatus is used to update the order management application with any changes in business status for a particular trading partner.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Credit 1..∞

Scenarios in which Acknowledge Credit is used

Feedback

OAGi and its members welcome your feedback.

UUID: 35a08faf74c54bd9b995d636d642e7d8

OAGIS Version 10.11.2

39 - BOD: Acknowledge Credit Status

The purpose of the AcknowledgeCreditStatus Business Object Document is to acknowledge receipt of the CreditStatus

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Credit Status 1..∞

Scenarios in which Acknowledge Credit Status is used

Feedback

OAGi and its members welcome your feedback.

UUID: 9acb7758cb5e48c6a2dbf824c1746889

OAGIS Version 10.11.2

40 - BOD: Acknowledge Credit Transfer

The purpose of the AcknowledgeCreditTransfer is to enable an application to request specific CreditTransfer information from another business application module. The response to the AcknowledgeCreditTransfer is the AcknowledgeCreditTransfer.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Credit Transfer 1..∞

Scenarios in which Acknowledge Credit Transfer is used

Feedback

OAGi and its members welcome your feedback.

UUID: 6b1bea9ae3f94cbbb688f8c90f0b114f

OAGIS Version 10.11.2

41 - BOD: Acknowledge Currency Exchange Rate

The purpose of the AcknowledgeCurrencyExchangeRate is to enable the passing of updates of currency exchange rates to other applications that have exchange rate tables.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Currency Exchange Rate 1..∞

Scenarios in which Acknowledge Currency Exchange Rate is used

Feedback

OAGi and its members welcome your feedback.

UUID: e85257e07cee4bb79e34d3eb56150270

OAGIS Version 10.11.2

42 - BOD: Acknowledge Customer Party Master

The purpose of the AcknowledgeCustomerPartyMaster is to facilitate keeping party information Acknowledgehronized that exists on separate data bases. The AcknowledgeCustomerPartyMaster allows the adding of new party and the modification of previously established CustomerPartyMaster.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Customer Party Master 1..∞

Scenarios in which Acknowledge Customer Party Master is used

Feedback

OAGi and its members welcome your feedback.

UUID: c56caf848e2f4862b7722f73d145283f

OAGIS Version 10.11.2

43 - BOD: Acknowledge Data Module

A data module that identifies a document written in accordance with S1000D.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Data Module 1..∞

Scenarios in which Acknowledge Data Module is used

Feedback

OAGi and its members welcome your feedback.

UUID: 13d3a0c71c2a494f9d265b36546be52f

OAGIS Version 10.11.2

44 - BOD: Acknowledge Debit Transfer

The purpose of the AcknowledgeDebitTransfer is to enable an application to request specific DebitTransfer information from another business application module. The response to the AcknowledgeDebitTransfer is the AcknowledgeDebitTransfer.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Debit Transfer 1..∞

Scenarios in which Acknowledge Debit Transfer is used

Feedback

OAGi and its members welcome your feedback.

UUID: 935daecb30fc459a8e00a874740acb89

OAGIS Version 10.11.2

45 - BOD: Acknowledge Dispatch List

The purpose of the AcknowledgeDispatchList Business Object Document is to acknowledge receipt of the DispatchList

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Dispatch List 1..∞

Scenarios in which Acknowledge Dispatch List is used

Feedback

OAGi and its members welcome your feedback.

UUID: 7177ae26f53944d0bc63f798ee1961fc

OAGIS Version 10.11.2

46 - BOD: Acknowledge Employee Work Schedule

The purpose of the AcknowledgeEmployeeWorkSchedule is to enable the Acknowledgehronization of Employee Work Schedule data that exists on separate data bases. The AcknowledgeEmployeeWorkSchedule allows the adding of new Employee Work Schedules as well as the modification of previously established Employee Work Schedules.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Employee Work Schedule 1..∞

Scenarios in which Acknowledge Employee Work Schedule is used

Feedback

OAGi and its members welcome your feedback.

UUID: 055703e5fbaf4686b2534d58e5a1900a

OAGIS Version 10.11.2

47 - BOD: Acknowledge Employee Work Time

The purpose of the AcknowledgeEmployeeWorkTime is to Acknowledge work time information for an employee from a data collection application to an ERP Human Resource application.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Employee Work Time 1..∞

Scenarios in which Acknowledge Employee Work Time is used

Feedback

OAGi and its members welcome your feedback.

UUID: 3cb5e5ac5f024a17bbba3d4b20a677b7

OAGIS Version 10.11.2

48 - BOD: Acknowledge Engineering Change Order

The purpose of the AcknowledgeEngineeringChangeOrder Business Object Document is to acknowledge receipt of the EngineeringChangeOrder

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Engineering Change Order 1..∞

Scenarios in which Acknowledge Engineering Change Order is used

Feedback

OAGi and its members welcome your feedback.

UUID: 8414f88c91be4d62afc1cc734ca047ff

OAGIS Version 10.11.2

49 - BOD: Acknowledge Engineering Work Document

The purpose of the AcknowledgeEngineeringWorkDocument is to enable an application to provide EngineeringWorkDocument from another business application module. The AcknowledgeEngineeringWorkDocument is provided in response to the ProcessEngineeringWorkDocument in order to accept or reject the request to process.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Engineering Work Document 1..∞

Scenarios in which Acknowledge Engineering Work Document is used

Feedback

OAGi and its members welcome your feedback.

UUID: 2463aab602f4411d8822719d3d2accfd

OAGIS Version 10.11.2

50 - BOD: Acknowledge Field

The purpose of the AcknowledgeField is to enable the validation of data that exists on separate application’s data bases. This BOD can cause on-line validation to occur or may be a single tool for Acknowledgehronizing data.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Field 1..∞

Scenarios in which Acknowledge Field is used

Feedback

OAGi and its members welcome your feedback.

UUID: dedeb4e4be384d5282c33ee5533f5ff2

OAGIS Version 10.11.2

51 - BOD: Acknowledge Fleet

A group of serialized product variants, usually in the form of vehicles, that move together, belong to the same owner, and/or belong to the same operational status.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Fleet 1..∞

Scenarios in which Acknowledge Fleet is used

Feedback

OAGi and its members welcome your feedback.

UUID: bdc5e2bc3a88465da78de241c5c875f5

OAGIS Version 10.11.2

52 - BOD: Acknowledge Freight Invoice

The purpose of the AcknowledgeFreightInvoice Business Object Document is to Acknowledge receipt of the Purchase Order and to reflect any changes. Commonly, the acknowledgment is generated by an order management application and transmitted to a purchasing or procurement application.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Freight Invoice 1..∞

Scenarios in which Acknowledge Freight Invoice is used

Feedback

OAGi and its members welcome your feedback.

UUID: 84f9f27252c44f1f86295788ea045409

OAGIS Version 10.11.2

53 - BOD: Acknowledge Hazardous Material Shipment Document

The purpose of the AcknowledgeHazardousMaterialShipmentDocument Business Object Document is to acknowledge receipt of the HazardousMaterialShipmentDocument

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Hazardous Material Shipment Document 1..∞

Scenarios in which Acknowledge Hazardous Material Shipment Document is used

Feedback

OAGi and its members welcome your feedback.

UUID: b0fbd524780241108d55e09fcc70d32e

OAGIS Version 10.11.2

54 - BOD: Acknowledge Inspect Delivery

The purpose of the AcknowledgeInspectDelivery is to supply InspectDelivery information for goods or services to another business application module. This BOD may is initiated by the sending system upon some event occurring. There are many possible business applications in several environments that may use this capability.

For example;

  1. A PurchaseOrder application could use this to send information to a Plant Data Collection application, or vice versa.
  2. An MRP, Inventory, Purchasing or Manufacturing business application could use this to communicate InspectDelivery information.
  3. A Laboratory Information System could send quality information to an Inventory application,
  4. A Quality Control application could send information to an MRP, Inventory, or Purchasing application.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Acknowledge 1..1
      Inspect Delivery 1..∞