Routine 62 should be extended but how?

Question

The following
description is from a FS,
A new invoice printout routine is needed. If an invoicing calendar is used for a customer then invoice output entry should not be automatically created.
Bill-to-party customer master data need to be checked for invoicing calendar. If calendar is found, then output entry should not be created.
Standard output routine (invoice released to accounting) applies in addition to the new logic.
Invoice print routine:
A new routine needs to be created for invoice output determination procedure. If invoice lists are used for a customer, the output for the invoice should not be automatically created.
Standard routine 62 (BillDoc:ReleasePost.) is valid and should be used as the basis for creating the new logic.
Customizing menu path:
Sales and Distribution à Basic Functions à Output Control à Output Determination à Maintain Output Determination for Billing Documents à Maintain Output Determination Procedure
Routine 62 should be extended to included the following:
Check if invoicing calendar is maintained for the bill-to-party (if entry exists in KNVV – PERRL) for the same sales area as in the invoice created.
Customer sales area data in KNVV – VKORG; KNVV – VTWEG; KNVV – SPART.
Partner number for the bill-to-party via invoice number from VBPA with PARVW BP. Sales area of the invoice VBRK – VKORG; VBRK – VTWEG; VBRK – SPART.
It is an enhancement to process Routine i can't understand it will u plz help out with corresponding
1. transactions 
2.
Action required
plz very urgent help me out.
Thank you.
Vishnu.

Answer 1

Not sure about what you asked but...
        DirContext objClasses = m_Ctx.getSchemaClassDefinition("o=bar,cn=foo");
        NamingEnumeration enum = objClasses.search("", null);
        while (enum.hasMore()) {
            SearchResult r = (SearchResult)enum.next();           
            System.out.println(r.getName());
        }Should enumerate objectClass attributes of object "o=bar,cn=foo".
If you want to enumerate all possible objectClass definitions that exist in
your schema, just bind to schema object and list its attributes.
Kulervo