SyncResponsePersonnel

The purpose of the SyncResponsePersonnel is to enable the SyncResponsehronization of employee data that exists on separate data bases between manufacturing and human resource applications.  The SyncResponsePersonnel allows the adding of new employees and their relevant data as well as the modification of previously established employees.

The SyncResponsePersonnel is used to facilitate the maintenance of human resource data in a manufacturing work force planning module.  This enables the workforce planning module to use current personnel information when creating finite production schedules.  The SyncResponsePersonnel can also be used by a project accounting application or a work order management application to assign qualified personnel or to perform resource planning.

Element information

Namespace: http://www.openapplications.org/oagis/10

Schema document: SyncResponsePersonnel.xsd

Type: SyncResponsePersonnelType

Properties: Global, Qualified, ID: oagis-id-f318002eb5d4480fadc3dc9c5f490654

Content

Sequence [1..1]
1. DataArea [1..1] Is where the information that the BOD message carries is provided, in this case SyncResponsePersonnel. The information consists of a Verb and one or more Nouns. The verb (SyncResponse) indicates the action to be performed on the Noun (Personnel).

Attributes

Name	Occ	Type	Description	Notes
releaseID	[1..1]	NormalizedStringType	OAGIS Release this BOD Instances belongs or the OAGIS release that the derivative work is based on.	from type BusinessObjectDocumentType
versionID	[0..1]	NormalizedStringType	Indicates the version of the given BOD definition.	from type BusinessObjectDocumentType
systemEnvironmentCode	[0..1]	SystemEnvironmentCodeContentType	Indicates whether this BOD is being sent in a "Test" or a "Production" mode. If the BOD is being sent in a test mode, it's information should not affect the business operation. However, if the BOD is sent in "Production" mode it is assumed that all test has been complete and the contents of the BOD are to affect the operation of the receiving business application(s).	Default value is "Production". from type BusinessObjectDocumentType
languageCode	[0..1]	LanguageCodeContentType	Indicates the language that the contents of the BOD is in unless otherwise stated.	Default value is "en-US". from type BusinessObjectDocumentType

Sample instance

<SyncResponsePersonnel releaseID="normalizedString">
   <ApplicationArea>
      <Sender>
         <LogicalID>normalizedString</LogicalID>
         <ComponentID>normalizedString</ComponentID>
         <TaskID>normalizedString</TaskID>
         <ReferenceID>normalizedString</ReferenceID>
         <ConfirmationCodes>...
         </ConfirmationCodes>
         <AuthorizationID>normalizedString</AuthorizationID>
      </Sender>
      <Receiver>
         <LogicalID>normalizedString</LogicalID>
         <ComponentID>normalizedString</ComponentID>
         <ID/>
      </Receiver>
      <CreationDateTime></CreationDateTime>
      <Signature>
         <!--any element-->
      </Signature>
      <ScenarioID>normalizedString</ScenarioID>
      <CorrelationID>normalizedString</CorrelationID>
      <BODID>normalizedString</BODID>
      <Extension>
         <AnyExtension>
            <!--any element-->
         </AnyExtension>
         <Amount/>
         <Code/>
         <DateTime></DateTime>
         <ID/>
         <Indicator>true</Indicator>
         <Measure/>
         <Name/>
         <Number>1.0</Number>
         <Quantity/>
         <Text/>
         <Time></Time>
         <ValueText>string</ValueText>
      </Extension>
   </ApplicationArea>
   <DataArea>
      <SyncResponse>
         <OriginalApplicationArea>...
         </OriginalApplicationArea>
         <ResponseCriteria>...
         </ResponseCriteria>
      </SyncResponse>
      <Personnel>
         <ID/>
         <IDSet>...
         </IDSet>
         <PersonName>...
         </PersonName>
         <Description/>
         <GenderCode>token</GenderCode>
         <MaritalStatusCode>token</MaritalStatusCode>
         <BirthDateTime></BirthDateTime>
         <DeathDateTime></DeathDateTime>
         <AgeMeasure>1.0</AgeMeasure>
         <LanguageCode>token</LanguageCode>
         <NationalityCountryCode>token</NationalityCountryCode>
         <Address>...
         </Address>
         <Communication>...
         </Communication>
         <EmployeeTypeCode>normalizedString</EmployeeTypeCode>
         <JobTitle/>
         <JobCode>normalizedString</JobCode>
         <Responsibility/>
         <DepartmentID>normalizedString</DepartmentID>
         <CategoryClassification>...
         </CategoryClassification>
         <ProfessionalQualification>...
         </ProfessionalQualification>
         <ProfessionalSkill>...
         </ProfessionalSkill>
         <Status>...
         </Status>
         <Classification>...
         </Classification>
         <EffectiveTimePeriod>..................
         </EffectiveTimePeriod>
         <PasswordEncryptedBinaryObject>GpM7</PasswordEncryptedBinaryObject>
         <HROrganizationIDs>...
         </HROrganizationIDs>
         <Facility>...
         </Facility>
         <GLEntityID>normalizedString</GLEntityID>
         <CostCenterID>normalizedString</CostCenterID>
         <WorkCenterID>normalizedString</WorkCenterID>
         <JobRestrictionCodes>...
         </JobRestrictionCodes>
         <ScheduleTypeCode>normalizedString</ScheduleTypeCode>
         <WorkShiftID>normalizedString</WorkShiftID>
         <WageTypeCode>normalizedString</WageTypeCode>
         <WageGroupCode>normalizedString</WageGroupCode>
         <OvertimeEligibleIndicator>true</OvertimeEligibleIndicator>
         <ContractReference>...
         </ContractReference>
         <Extension>.......................................
         </Extension>
      </Personnel>
   </DataArea>
</SyncResponsePersonnel>