Business Function Builds During Package Build
When you build business functions as part of the package build, the system performs the same process as if you had manually run Oracle's JD Edwards EnterpriseOne BusBuild program (selected Build from the Global Build menu) after you built the package.
The system retrieves source and header information from the package (from the source/source64 and include/include64 directories), compiles it, and stores it in the bin32, obj, and lib32 directories or bin64, obj64, and lib64 if building with a 64-bit package. The system builds business functions in the package, not on the workstation. If you select the Compress Package option, the system compresses the business functions after it builds them.
These guidelines apply to the path code, foundation, and destination for the business function build:
When building business functions, use the path code that you defined in the package.
The foundation is either the same as the foundation that is included in the package or, for an update package, it is the foundation for the parent package.
Build output is directed to the bin32, obj, and lib32 directories of the package itself; or if building a 64-bit package, then the bin64, obj64, and lib64 directories of the package.
When building a full package, or when building an update package that includes a business function, always build business functions; otherwise, the consolidated DLLs included in the package will not be current.
For update packages, the system builds each business function individually. After it builds an individual business function, the system performs a global link for that object and all other objects that are in the same consolidated DLL. The global link affects all objects in the check-in location for the path code of that package.