12:24 Ou BZ ES “© customer account Picked fom Sales Order and other entries except Ta are peed from VKOA Settings. VOR Visor Sle & Dstbution KOFE for acount determination for RAG or Costomeraich pices rom Cstomer Mast, A8G 0 Mater nhich is iced tom Material Master Account keys ae Pcked om Png, Procedure. Taxaccounts te picked from Conlin Tabin Sales Order. Condon ‘Record are maintains in VEL, Tae reat G'S are Ike to Account ey in OBA. “These account key ae linked to Pricing Procedure ‘Account Determination in OBYC 8 OB403tthe ime of Transport Request "wen we do any changes or doing any contigaraion then we have to save in Transport Request inGolden Gent and then have to lense to ual, Later t Presuion. Detar release TRWe ave t Cros check ith Prosuton Chen to Avot Overt suet. Fertsamele, Development| Production Transaction key - 5% TaansactionKey- 654 Covsassgnedin Bx 19 sagen BX. 25 if do any change or configuration like add one mare GL in BSK in Development Client and save in ‘TRand then release TR to Production then all 25 GL’s gone in Producten and willbe 20. Tiss ‘because of overwriting by new change in Development. Now the GL’s as Gs asignedin 88% = 20 GUs assigned in BX 20 Ife wane ge back all25 TR's in Production then look for Old TR which has been released with 25, ous. So always scare fll before release TR with ths setting to Production. heck with Production Client and Development Client. For instance take above example; we have 19 G's in DEV and 25, GGUS in PRD. inthis case ist copies the rest 6 U's to DEV marwally and then does required change ‘or configuration and save in TR which will be released to PRD later. Note This kind of Precaution has to take when we do settings for OBYC, OB40 and Validations & Substtuions. $3 SCRIBD Trusted by over 1 million members