02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 6: Third Party Integrations<br />

Object Codes for Traditional Objects<br />

360<br />

Object Code Description<br />

JDEVOV Vocabulary overrides.<br />

JDEMNU Menus.<br />

JDEWWR WorldWriters.<br />

JDEFST FASTR.<br />

JDEPRO Processing Options.<br />

JDEWCS World Case.<br />

JDNSPC For traditional objects (like RPG, CLP), required to update the Software Version<br />

Repository in PeopleSoft World for traditional objects.<br />

Use the following object codes delivered with <strong>Implementer</strong> to manage PeopleSoft World<br />

traditional objects. You must first activate the object codes (in Work with Object Codes) for all<br />

applicable environments.<br />

Object Code/ Description<br />

JDEDSPF Display file.<br />

JDEPF Physical file.<br />

JDELF Logical file.<br />

JDECLP CL program.<br />

JDERPG RPG program.<br />

JDEPRTF Generates printer file overrides during promotion (valid for local compiles only).<br />

With the exception of the JDEPRTF object code, each object code has the special characteristic<br />

JDNSPN. The JDEPRTF object code has the special characteristic JDNPRTF, which adopts the<br />

same functionality as the JDNSPC special characteristic. All traditional objects managed by<br />

<strong>Implementer</strong> with these object codes/special characteristics update the Software Version<br />

Repository (SVR) in PeopleSoft World during check out and promotion. The objects must<br />

exist as member IDs in the SVR file. When working with a new object, you must first create<br />

the member ID in the SVR file to enable <strong>Implementer</strong> updates.<br />

IMPORTANT Only one copy of JDE files F9801 and F9802 can exist across your<br />

environments. In other words, the production, QA, and development environments<br />

share these two files; multiple copies of these files cause incorrect SVR updates.

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

Saved successfully!

Ooh no, something went wrong!