Skip to main content

COPA Characterestic Hierarchy

Many times in the past, other application support teams and even business teams had requested for soft copy of the characteristic hierarchy, so that they can replicate information in the hierarchical way SAP is showing. The following tables store the details of the tree structure TKCHH SAP-EIS: Hierarchy header TKCHHT SAP-EIS: Texts for hierarchy header TKCHN SAP-EIS Hierarchy nodes TKCHNT SAP-EIS: Hierarchy node texts TKCHV SAP-EIS: Hierarchy variants TKCHVT SAP-EIS: Description of hierarchy variants TKCHW SAP-EIS: Hierarchy data The tree structure can be replicated using the TKCHW table, which stores the tree relationship.

Comments

Post a Comment

Popular posts from this blog

Vendor Consignment Business Process

Wikipedia offers a very simple definition for consignment . It is a process of placing a thing in the hand of another, but retaining the ownership until the goods are sold or used. In SAP consignment business process can be implemented very easily using the following steps. Activate Consignment inforecords using tcode OMEV. This activates the consignment prices to be picked up using the consignment info records. configure a special procurement type using IMG->Production->MRP->Master Data->Define special procurement type. In OBYC configure the consignment payables account (transaction KON). Assign the special procurement type created in step 2 to all the materials that are to use the consignment process. This is done in the MRP2 view of the material master maintenance transaction Create Consignment info record using tcode ME11. Select info category as consignment. Create general data, Purchase Org data and conditions. Conditions allow you to create time dependent prices. Cre...
16 comments
Read more

Stock Differences in HU (Handling Unit)

This blog post might help you to solve the problem with these messages. HUGENERAL 017 Handling unit &1 has the status "goods issue posted", cannot be changed HUFUNCTIONS 251 No posting-relevant material items could be found Many times it happens that the standard functionality provided by SAP is not sufficient. IN HU if customisations have been done, it is possible that, you end up with some data inconsistancy. The worst part about this is that not much is available in SAP or even internet. I learnt these hard way. The solution might look very simple, but it has consumed quite a lot of tense days. This could be due to some MDE customisations also. The above messages might appear if you are trying to transfer HU from blocked to unrestricted or vice versa using VLMOVE. Or if you are trying to pick a HU from stock. What happened in my case is that the inventory stock was transferred to Blocked stock, but the HU was not updated. So, the following standard transactions gives...
2 comments
Read more

Unlimited overdelivery tolerance flag is reset!

Haaaaa. I am back after after a looooooong break. I have decided to keep posting more regularly now :-). This one is what we usually face after the stacks. I like to call it PSM (Post Stack Misbehaviour). Sap Note 1580025 in Stack 10 caused a problem where by, any change to Purchase Order item (delivery date, schedule qty, Purchase order qty, price etc.), resets the unlimited over delivery tolerance flag. Usually the unlimited over delivery tolerance flag is defaulted from Inforec. This might create nasty issues for the business, where business might be expecting the GR to go through smoothly, it will end up in error.The probelm is solved by applying note 1644491.
Post a Comment
Read more