13.07.2015 Views

SCT Banner Human Resources / Release Guide / 7.0

SCT Banner Human Resources / Release Guide / 7.0

SCT Banner Human Resources / Release Guide / 7.0

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix C Using the Common Person API in <strong>Human</strong> <strong>Resources</strong>IntroductionAppendix CUsing the Common Person API in <strong>Human</strong><strong>Resources</strong>IntroductionWith <strong>Banner</strong> <strong>7.0</strong>, there are two sets of API's that are provided with the <strong>Human</strong><strong>Resources</strong> application set. They are the Common Person API and the EmployeeAPI. This section will generally define the functionality and special notes associatedwith those processes. Further technical descriptions of API processing can be foundin the API Reference <strong>Guide</strong>.Common Person APIThe processing of biographic and demographic data, associated with a person oremployee record, has been revised so that it is consistent with other <strong>Banner</strong>applications and so that common processing can be executed. The API is executedwhenever you select, insert, update, or delete data.The focal point of this information resides on the Identification Form (PPAIDEN).All data blocks on this form execute the common business logic. These include:• Current Identification• Alternate Identification• Address• Biographical• Emergency ContactTwo other forms that allow the creation of a PIDM, within the <strong>Human</strong> <strong>Resources</strong>application include the New Hire Form (PEAHIRE) and the One-Time PaymentForm (PEA1PAY). Both of these forms process core person data and therefore, havehad the API logic applied.January 2005 <strong>Human</strong> <strong>Resources</strong>/Position Control <strong>Release</strong> <strong>7.0</strong>Confidential <strong>Release</strong> <strong>Guide</strong> 361

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!