CURRENCY (USDN)

HELLO EXPERTS,
For the first time our company want to procure material from CHINA. So I have to use USDN (US dollar) in PO. But before that all my company code and vendor's currency is maintain in INR (INDIAN RUPEES ) only. So what are the changes in settings I have to do so that I m able to make an PO ( Purchase Order) in USDN currency from china vendor.
plz ans me.
REGARDS
raghu

hi,
maintain exchange rate for the desires currency in OB08.
Maintain ordering currency as USD in Vendor master.
regards
Manish Joshi
Edited by: MANISH JOSHI on Sep 15, 2008 9:10 AM

Similar Messages

Consignment settlement using currency USDN

Dear All,
I have a question in regards to consignment settlement using currency type USDN.
**My client would want to use 5 decimal places and hence using USDN currency type**
At present for consignment process, we are maintaining a Cons info record with 5 decimals using USDN currency type.
And apparently this is the only place where we can control the currency through the whole process till settlement.
Once PO, MIGO and the transfer posting is done, during the settlement process MRKO, the final document currency is obtained in USDN
Is there any way we can obtain the document currency in USD and yet have 5 decimals? like having a user exit

Hi,
Before MRKO, check following;
1. ME11 - Purchase Info Record with Info Category "Consignment" (In PIR, maintain Net Price as well as Tax Code)
2. MB1B - Transfer stock from Consignment to Unrestricted (own stock), using 411 K
3. MRM1 - Maintain condition record for Output type KONS i.e. Consignment
4. MRKO - Refer the Material document of 411 K and In selection screen select "Withdrawals Not Settled" and Under procesing select "Settle" radio button.

USD and USDN currency invoices payment through F110

Hi all,
Invoices are posted in both USDN and USD in our system.
I am able to process payment in USD in T code F-58, for invoices created in both currency USDN and USD. But in F110, USDN invoices are not included in the proposal due to the error "No valid payment procedure". I would appreciate your kind help to resolve the error.
Regards
Sri.

Hi Sri,
Have a set configure in FBZP correctly. If not, set configuration in FBZP t.code in Payment Method in Country tab and Payment Method in Company Code tab correctly as for Check Payment.
and assign correct House Bank and Payment Method "C" in the Vendor Master Data.
May be this information is useful to you
If you have any doubt feel free to ask
Regards
Surya

Currency scaling

Hi!
The queries are showing different values from the Cube.The values are showing scaled. For example, in the query I've got $155 and in the Cube $155000. The key figure are not scaled in the Query Designer. I have this issue in all queries with currency fields.
I tried to transfer the global settings and exchange rates from R/3 but the issue was not solved.
Does anybody knows what's could happening?
Thanks in advance.
Regards.

Hi Pepe,
A currency keyfigure should always be assoicated with corresponding currency key defined in the keyfigure definition. It can either be fixed currency 'USD' or a variable 0CURRENCY filled at record level with corresponding currency key from transactional system. This allows runtime currency conversions.
For simplicity, take two currencies USD (2 decimals) and USDN (high accuracy 5 decimals). A value $2000.50 will be internally stored as "200050" with associated key USD (or) "200050000" with associated key USDN
In transactional system, if a field is entered and processed as USDN. the underlying value stored in Table would be "200050000". At run time the GUI display or query display associates this value with currency and displays it as 2000.50000.
Some times, during the process of transferring this value into BI, if this source USDN field value is directly assigned to a keyfigure with fixed currency USD without proper explicit currency conversion, the source currency (USDN) association with the value is lost. The value that is passed to the target field will still be "200050000" but the target currency will be USD (2 decimals). At runtime the query display or the GUI display reads the underlying value and displays it as $2000500.00
To fix this you need to find where exactly the currency key is being dropped during transformations and write some explicit logic to convert the underlying value accordingly from USDN to USD. i.e 200050000 USDN = 200050 USD with conversion rate of 1/1000
You can use function module RSW_CURRENCY_TRANSLATION and pass the source value and source currency and the currency translation type ( in this case USDN to USD defined in table RSCURTRT -using transaction RSCUR ) to get corresponding target value and target currency.
Hope it helps
Uday Pothireddy

Increasing currency from 2 to 3 decimal points

Dear all,
I would like to know how to make the currency view in the expense report increased from 2 to 3 decimal points as km/miles rate we have here is $0.335 per mile. Also the USD is used for 5 other countries. As of now it is showing as 0.34, however this is a manipulation of actual data, Ex. for 10 kms it shows rate 0.34 x miles 10 = $3.35.
Any quick response would be of great help.
Regards,
LN Bhattacharya

Yes this is a known issue as the problem is, that the USD is a currency with 2 decimals, but government allowes to reimburse 0.375 USD taxfree. The output on the travel form is in a single currency: the USD with 2 decimals. One workaround is to create a currency USDN for the decimilisation to work with 3 places - see the note 446116
A single expense category like miles per diems is calculated in accounting program RPRTEC00 and stored in one table (PAUFA for miles).
If currency in T706F (USDN) differs from trip currency (USD), RPRTECC00 converts the amounts from T706F into trip currency (done by FI-function 'CONVERT_TO_LOCAL_CURRENCY'). Amounts in the list are presented in this trip currency but rounding is possible with adjustment in V_T001R as PREC can handle this conversion with factors defined here.
Hope it helps!
Thanks
Sally

Currencies with 5 decimals

Hi,
For pricing reason, I need to define 5 decimals in some currencies (USD, ARS, EUR and DEM). I was reading some information about it, and the solution I found is to create one Z currency for each estandar currency (USDN, EURN, AR5 and DEM5).
I am not sure about the problem this procedure can cause in the system. Suppose that the local currency is USD, so I will have the SD invoice in USDN. The document will be managed as a document in foreing currency. I wondering if I will also have rounding differences in the cIearing document, and for some report I will have to adapt the information.
Does anyone have implemented this solution?
Which problems can cause?
Any recomendation about that?
Thanks,
Cecilia

Hi,
check the following threads:
Currency in 5 decimal places.
Custom Table Currency field with 5 decimals
Any changes you going to made in OY04 is affecting cross clients.
It is NOT recommended that when postings have already been made, that a
change in the currency be done, as amounts posted can become invalid or
incorrect as a result which is most critical in production environment.
The decimal places setting in OY04 is limited to 5. It is not possible to set more decimal places in standard SAP.
Technial explanation is also described on note 434349, 137626 and 126857
Hope this was helpful for you.
Regards,
Cristiano

PO is not creating in system

Hello Experts,
Iu2019m trying to create a PO through u2018BAPI_PO_CREATE1u2019. Iu2019ve gathered all the structure and fields which this bapi needs to create PO. When I call this BAPI in my report program the whole code get execute but I never get any message which tells me that a PO has been created in the system. Can somebody please tell me what is wrong with my code OR am I missing something in it.
For reference here is my code.
===========================================================
REPORT zad_bapi_po_create                      .
Constant Declaration for BAPI *****************
Data: l_bsart like mepo_topline-bsart value 'NB',
      l_bsart1 like mepo_topline-bsart value 'ZNB'.
Constants: c_ekorg like mepo1222-ekorg value 'POMR',
           c_ekgrp like mepo1222-ekgrp value 'PG1',
           c_bukrs like ekko-bukrs value 'SBPL',
           c_x value 'X'.
Internal table Declaration for BAPI *****************
Data:begin of i_tab occurs 0,
     verkf like ekko-verkf,
     verkf1 like ekko-verkf,
     lifnr like ekko-lifnr,
     werks like ekpo-werks,
     ebelp1 like ekpo-ebelp,
     matnr like ekpo-matnr,
     idnlf like ekpo-idnlf,
     menge(16),
     bprme like ekpo-bprme,
     lewed like ekpo-lewed,
     netpr(13),
     currkey(5),
     ebeln like eord-ebeln,
     ebelp like eord-ebeln,
     verkf2 like ekko-verkf,
     kalsk like lfm1-kalsk,
     bsart like mepo_topline-bsart,
     lifnr1 like ekko-lifnr,
     flag(1),
     pstyp like ekpo-pstyp,
     end of i_tab.
Data Declaration for BAPI *****************
DATA: BEGIN OF pohead OCCURS 10.
        INCLUDE STRUCTURE bapimepoheader.
DATA: END OF pohead.
DATA: BEGIN OF poheadx OCCURS 10.
        INCLUDE STRUCTURE bapimepoheaderx.
DATA: END OF poheadx.
*EXPPURCHASEORDER
DATA: BEGIN OF ponum.
        INCLUDE STRUCTURE bapimepoheader.
DATA: END OF ponum.
DATA: BEGIN OF poitem OCCURS 100.
        INCLUDE STRUCTURE bapimepoitem.
DATA: END OF poitem.
DATA: BEGIN OF poitemx OCCURS 100.
        INCLUDE STRUCTURE bapimepoitemx.
DATA: END OF poitemx.
DATA: BEGIN OF poitemsch OCCURS 100.
        INCLUDE STRUCTURE bapimeposchedule.
DATA: END OF poitemsch.
DATA: BEGIN OF poitemschx OCCURS 100.
        INCLUDE STRUCTURE bapimeposchedulx.
DATA: END OF poitemschx.
DATA: BEGIN OF errmsg OCCURS 10.
        INCLUDE STRUCTURE bapiret2.
DATA: END OF errmsg.
DATA : errflag.
START-OF-SELECTION.
refresh pohead.
refresh poheadx.
clear pohead.
refresh poitem.
refresh poitemx.
pohead-DOC_type = i_tab-bsart.
pohead-vendor = i_tab-lifnr.
pohead-purch_org = c_ekorg.
pohead-creat_date = sy-DATUM.
pohead-pur_group = c_ekgrp.
pohead-comp_code = c_bukrs.
pohead-sales_pers = i_tab-verkf2.
pohead-doc_Date = sy-datum.
pohead-langu = sy-langu.
pohead-currency = 'USDN'.
pohead-item_intvl = ''.
append pohead.
poheadx-doc_type = c_x.
poheadx-vendor = c_x.
poheadx-purch_org = c_x.
poheadx-pur_group = c_x.
poheadx-comp_code = c_x.
poheadx-sales_pers = c_x.
poheadx-item_intvl = c_x.
poheadx-doc_date = c_x.
poheadx-currency = c_x.
poheadx-langu = c_x.
append poheadx.
refresh poitem.
clear poitem.
refresh poitemsch.
clear poitemsch.
refresh poitemschx.
clear poitemschx.
poitem-po_item = '0010'.
poitem-material = '40-210'.
poitem-quantity = '1'.
poitem-po_unit = 'ST'.
poitem-net_price = '1'.
poitem-no_rounding = 'X'.
poitem-plant = '1200'.
poitem-info_upd = ''.
poitem-item_cat = '0'.
poitem-vend_mat = ''.
append poitem.
clear poitemx.
poitemx-po_item = '0010'.
poitemx-MATERIAL = c_x.
poitemx-QUANTITY = c_x.
poitemx-PO_UNIT = c_x.
poitemx-NET_PRICE = c_x.
poitemx-NO_ROUNDING = c_x.
poitemx-PLANT = c_x.
poitemx-GR_TO_DATE = c_x.
poitemx-INFO_UPD = c_x.
poitemx-tax_code = c_x.
poitemx-item_cat = c_x.
POITEMx-ACCTASSCAT = c_x.
poitemx-AGREEMENT = 'X'.
poitemx-AGMT_ITEM = 'X'.
poitemx-VEND_MAT = c_x.
append poitemx.
poitemsch-po_item = '0010'.
poitemsch-sched_line = '0001'.
poitemsch-delivery_date = sy-datum.
poitemsch-quantity = '1'.
append poitemsch.
poitemschx-po_item = '0010'.
poitemschx-sched_line = '0001'.
poitemschx-po_itemx = c_x.
poitemschx-delivery_Date = c_x.
poitemschx-quantity = c_x.
append poitemschx.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
    poheader                     = pohead
    POHEADERX                    = poheadx
POADDRVENDOR                 =
TESTRUN                      =
MEMORY_UNCOMPLETE            =
MEMORY_COMPLETE              =
POEXPIMPHEADER               =
POEXPIMPHEADERX              =
VERSIONS                     =
NO_MESSAGING                 =
NO_MESSAGE_REQ               =
NO_AUTHORITY                 =
NO_PRICE_FROM_PO             =
IMPORTING
EXPPURCHASEORDER             =
   EXPHEADER                    = ponum
EXPPOEXPIMPHEADER            =
TABLES
   RETURN                       = errmsg
   POITEM                       = poitem
   POITEMX                      = poitemx
POADDRDELIVERY               =
   POSCHEDULE                   = poitemsch
   POSCHEDULEX                  = poitemschx
POACCOUNT                    =
POACCOUNTPROFITSEGMENT       =
POACCOUNTX                   =
POCONDHEADER                 =
POCONDHEADERX                =
POCOND                       =
POCONDX                      =
POLIMITS                     =
POCONTRACTLIMITS             =
POSERVICES                   =
POSRVACCESSVALUES            =
POSERVICESTEXT               =
EXTENSIONIN                  =
EXTENSIONOUT                 =
POEXPIMPITEM                 =
POEXPIMPITEMX                =
POTEXTHEADER                 =
POTEXTITEM                   =
ALLVERSIONS                  =
POPARTNER                    =
if sy-subrc eq 0.
write:/ 'PO Created successfully!!!'.
else.
write:/ 'Error Occured during PO Creation'.
endif.
===========================================================
Thanks,

Bapi's do not set sy-subrc. The only way to check if it was succesfull is to loop into the return table for error messages:
You have to use BAPI_TRANSACTION_COMMIT after calling BAPI_PO_CREATE1:
    READ TABLE errmsg TRANSPORTING NO FIELDS
                        WITH KEY type = c_e.
    IF NOT sy-subrc IS INITIAL.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = c_x.
ENDIF.

Sales Order Creation using BAPI_BUSPROCESSND_CREATEMULTI

Hi,
I am trying to create sales order using BAPI_BUSPROCESSND_CREATEMULTI.
when I create a sales order using above mentioned BAPI it is creating empty sales order,It is not passing the values from the code to the sales order.
In BAPI_BUSPROCESSND_CREATEMULTI   Return parameter i m getting Message
     S     CRM_M_ESSAGES     005     A log has been generated for single document     $000001     000001
Following are the List of Function modulesi have used in my code
1 ) GUID_CREATE
2) BAPI_BUSPROCESSND_CREATEMULTI
3) BAPI_BUSPROCESSND_SAVE
4) BAPI_TRANSACTION_COMMIT
kindly help me to resolve the same
Thanks

Hi Prerna,
still Empty Sales order is creating
This is my code
************HEADER-GUID*********
CALL FUNCTION 'GUID_CREATE'
IMPORTING
     EV_GUID_16       = LV_GUID
    EV_GUID_22       =
    EV_GUID_32       = LV_GUID1.
**********ITEM-GUID***********
CALL FUNCTION 'GUID_CREATE'
IMPORTING
EV_GUID_16       =
EV_GUID_22       =
   EV_GUID_32       = LV_GUID2
********SCHEDULELINE*******
CALL FUNCTION 'GUID_CREATE'
    IMPORTING
     EV_GUID_16       =
     EV_GUID_22       =
      EV_GUID_32       = LV_GUID3
CALL FUNCTION 'CRM_PRP_IL_GET_HANDLE'
IMPORTING
    EV_HANDLE = LV_HANDLE.
CALL FUNCTION 'CRM_ACTIVITY_MAIN_PARTNER_GET'
EXPORTING
    IV_PROCESS_TYPE                   = 'ZDON'
    IV_CRMT_SUBOBJECT_CATEGORY        = 'BUS2000115'
IMPORTING
   EV_DYNP_FCT_1                     = lv_partner_fct1
   EV_DYNP_FCT_2                     = lv_partner_fct2
   EV_DYNP_FCT_3                     = lv_partner_fct3
   EV_DYNP_FCT_4                     = lv_partner_fct4
EXCEPTIONS
   PROCESS_TYPE_DOES_NOT_EXIST       = 1
   DETERM_PROC_DOES_NOT_EXIST        = 2
   NO_MAIN_PARTNER                   = 3
   OTHERS                            = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
***********DATA IN HEADER*********
WA_HDR-GUID = LV_GUID1.
WA_HDR-HANDLE = LV_HANDLE.
WA_HDR-PROCESS_TYPE = 'ZDON'.
APPEND WA_HDR TO IS_HEADER.
INPUT FIELDS HEADER**************
CLEAR WA_INPUT_FIELDS.
CLEAR IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
WA_INPUT_FIELDS-FIELDNAME = 'GUID'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
WA_INPUT_FIELDS-FIELDNAME = 'HANDLE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
WA_INPUT_FIELDS-FIELDNAME = 'PROCESS_TYPE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
***********DATA IN ITEM*********
WA_ITEM-GUID = LV_GUID2.
WA_ITEM-HANDLE = LV_HANDLE.
WA_ITEM-HEADER = LV_GUID1.
WA_ITEM-ORDERED_PROD = 'H10'.
WA_ITEM-DESCRIPTION = 'Trading Good 1'."product name
WA_ITEM-ITM_LANGUAGE = 'EN'.
WA_ITEM-ITM_TYPE = 'LEAD'.
WA_ITEM-MODE = 'A'.
INSERT WA_ITEM INTO TABLE IS_ITEM.
******INPUT FIELDS ITEM****************
CLEAR WA_INPUT_FIELDS.
CLEAR IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'GUID'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'HANDLE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'HEADER'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'ORDERED_PROD'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'DESCRIPTION '.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'ITM_LANGUAGE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'number_int'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'ITM_TYPE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
***********DATA IN SALES*********
WA_SALES-REF_HANDLE = LV_HANDLE.
WA_SALES-REF_GUID = LV_GUID1.
WA_SALES-PO_NUMBER_SOLD = '10006'.
WA_SALES-YOUR_REF_SHIP = '10006'.
APPEND WA_SALES TO It_SALES.
************INPUT FIELDS SALES************
CLEAR WA_INPUT_FIELDS.
CLEAR IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'SALES'.
WA_INPUT_FIELDS-FIELDNAME = 'REF_HANDLE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'SALES'.
WA_INPUT_FIELDS-FIELDNAME = 'REF_GUID'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'SALES'.
WA_INPUT_FIELDS-FIELDNAME = 'PO_NUMBER_SOLD'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'SALES'.
WA_INPUT_FIELDS-FIELDNAME = 'YOUR_REF_SHIP'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
************DATA IN PARTNER *********
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-REF_HANDLE = LV_HANDLE.
WA_PARTNER-PARTNER_FCT = lv_partner_fct1.
WA_PARTNER-PARTNER_NO = '10006' .
APPEND WA_PARTNER TO IT_PARTNER.
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-REF_HANDLE = LV_HANDLE.
WA_PARTNER-PARTNER_FCT = lv_partner_fct2.
WA_PARTNER-PARTNER_NO = '10006' .
APPEND WA_PARTNER TO IT_PARTNER.
if lv_partner_fct3 is initial.
   lv_partner_fct3 = lv_partner_fct2 + 1.
endif.
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-REF_HANDLE = LV_HANDLE.
WA_PARTNER-PARTNER_FCT = lv_partner_fct3.
WA_PARTNER-PARTNER_NO = '10006' .
APPEND WA_PARTNER TO IT_PARTNER.
if lv_partner_fct4 is initial.
   lv_partner_fct4 = lv_partner_fct3 + 1.
endif.
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-REF_HANDLE = LV_HANDLE.
WA_PARTNER-PARTNER_FCT = lv_partner_fct4.
WA_PARTNER-PARTNER_NO = '10006' .
APPEND WA_PARTNER TO IT_PARTNER.
*INPUT FIELDS PARTENER
CLEAR WA_INPUT_FIELDS.
CLEAR IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'REF_GUID'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'REF_HANDLE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_FCT'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_NO '.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
***********DATA IN ORGMAN*********
WA_ORG-REF_GUID = LV_GUID1.
WA_ORG-REF_HANDLE = LV_HANDLE.
WA_ORG-DIS_CHANNEL = '10'.
WA_ORG-DIVISION = '10'.
WA_ORG-SALES_ORG = 'BP_SALES'.
WA_ORG-SALES_OFFICE = 'BP_SO_CENTER'.
WA_ORG-SALES_ORG_RESP = 'BP_SALES'.
APPEND WA_ORG TO IT_ORG.
ORGMAN INPUT FIELDS*****************
CLEAR WA_INPUT_FIELDS.
CLEAR IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
WA_INPUT_FIELDS-FIELDNAME = 'REF_GUID '.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
WA_INPUT_FIELDS-FIELDNAME = 'REF_HANDLE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
WA_INPUT_FIELDS-FIELDNAME = 'DIS_CHANNEL'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
WA_INPUT_FIELDS-FIELDNAME = 'DIVISION'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
WA_INPUT_FIELDS-FIELDNAME = 'SALES_ORG'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
WA_INPUT_FIELDS-FIELDNAME = 'SALES_OFFICE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
WA_INPUT_FIELDS-FIELDNAME = 'SALES_ORG_RESP'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
***********DATA IN PRODUCT*********
WA_PROD-REF_GUID = LV_GUID2.
WA_PROD-REF_HANDLE = LV_HANDLE.
WA_PROD-PROCESS_QTY_UNIT = 'ONE'.
APPEND WA_PROD TO IT_PROD.
*INPUT FIELDS PRODUCT
CLEAR WA_INPUT_FIELDS.
CLEAR IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'D'.
WA_INPUT_FIELDS-OBJECTNAME = 'PRODUCT_I'.
WA_INPUT_FIELDS-FIELDNAME = 'REF_GUID'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'D'.
WA_INPUT_FIELDS-OBJECTNAME = 'PRODUCT_I'.
WA_INPUT_FIELDS-FIELDNAME = 'REF_HANDLE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'D'.
WA_INPUT_FIELDS-OBJECTNAME = 'PRODUCT_I'.
WA_INPUT_FIELDS-FIELDNAME = 'PROCESS_QTY_UNIT'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
***********DATA IN SCHED*********
WA_SCHED-ITEM_GUID = LV_GUID2.
WA_SCHED-GUID = LV_GUID4 .
WA_SCHED-HANDLE = LV_HANDLE.
WA_SCHED-QUANTITY = '5'.
APPEND WA_SCHED TO IT_SCHED.
*INPUT FIELDS SCHEDULE LINE
CLEAR WA_INPUT_FIELDS.
CLEAR IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'D'.
WA_INPUT_FIELDS-OBJECTNAME = 'SCHEDLIN_I'.
WA_INPUT_FIELDS-FIELDNAME = 'ITEM_GUID'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'D'.
WA_INPUT_FIELDS-OBJECTNAME = 'SCHEDLIN_I'.
WA_INPUT_FIELDS-FIELDNAME = 'GUID'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'D'.
WA_INPUT_FIELDS-OBJECTNAME = 'SCHEDLIN_I'.
WA_INPUT_FIELDS-FIELDNAME = 'HANDLE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'D'.
WA_INPUT_FIELDS-OBJECTNAME = 'SCHEDLIN_I'.
WA_INPUT_FIELDS-FIELDNAME = 'QUANTITY '.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'D'.
WA_INPUT_FIELDS-OBJECTNAME = 'SCHEDLIN'.
WA_INPUT_FIELDS-FIELDNAME = 'LOGICAL_KEY'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'D'.
WA_INPUT_FIELDS-OBJECTNAME = 'SCHEDLIN'.
WA_INPUT_FIELDS-FIELDNAME = 'MODE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
***********DATA IN PRICING********
WA_PRICING-REF_HANDLE = LV_HANDLE.
WA_PRICING-REF_GUID = LV_GUID2.
WA_PRICING-CURRENCY = 'USDN'.
APPEND WA_PRICING TO IT_PRICING.
*INPUT FIELDS PRICING
CLEAR WA_INPUT_FIELDS.
CLEAR IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'D'.
WA_INPUT_FIELDS-OBJECTNAME = 'PRICING_I'.
WA_INPUT_FIELDS-FIELDNAME = 'REF_HANDLE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'D'.
WA_INPUT_FIELDS-OBJECTNAME = 'PRICING_I'.
WA_INPUT_FIELDS-FIELDNAME = 'REF_GUID '.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'D'.
WA_INPUT_FIELDS-OBJECTNAME = 'PRICING_I'.
WA_INPUT_FIELDS-FIELDNAME = 'CURRENCY'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
IMPORTING
    EV_LOG_HANDLE           =
TABLES
    HEADER                  = IS_HEADER
   ITEM                     = IS_ITEM
   SALES                    = It_SALES
   PARTNER                 = IT_PARTNER
   ORGANISATION             = IT_ORG
   INPUT_FIELDS              = IT_INPUT_FIELDS
   CREATED_PROCESS         =   ITAB_CREATED_PROCESS
   RETURN                  = IT_RETURN
   PRODUCT                  = IT_PROD
   SCHEDULELINE             = IT_SCHED
   PRICING_ITEM             = IT_PRICING
W_OBJECT_TO_SAVE-GUID = lv_guid1.
APPEND W_OBJECT_TO_SAVE TO It1_object_to_save.
CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
EXPORTING
    UPDATE_TASK_LOCAL = SPace
    SAVE_FRAME_LOG    = 'X'
IMPORTING
   LOG_HANDLE        = LV_LOG_HANDLE
TABLES
    OBJECTS_TO_SAVE   = It1_object_to_save
    SAVED_OBJECTS     = i_saved_objects
    RETURN            = IT_RETURN1.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
    WAIT          = 'X'
IMPORTING
    RETURN        = IT_RET2
if sy-subrc = 0.
write : / 'Sales Order Created'.
endif.
thanks

Saudi Arabia Payroll

Hello Experts,
Now I am working on saudi arabia payroll in 6.0. I need to create wts under country code 24 (saudi arabia). but i didnt find standard WTs there. If i change molga to 99 (international), wts are available.
can i change molga to 99 and create WTs for saudi under payroll international.
If this is the case, Which schema should we use here?
Please guide us.
Thanks and Regards.
Sam

in IMG node check
PM PA PY data check
Define hourly rates with several decimal places
In this step, you define an alternative currency to be used for wage type amounts in the infotype Basic Pay (0008).
The default currency for wage types in the infotype Basic Pay is taken from the currency set for the company code. You can, however, set up the default currency so that it is dependent on the country grouping, pay scale type, pay scale area and employee subgroup grouping for collective agreement provision.
You can also set up a currency with additional decimal places. This allows you to enter amounts for wage types that have more than the usual number of decimal places.
You should also maintain the amounts in the the pay scale dependent table for wage types.
The currency for the annual salary should be taken from the company code.
Example
A certain US-American collective agreement demands that the pay for hourly paid workers is given and paid to the nearest hundreth cent.
The currency for the wage type amounts for these employees should be given as a default value in the basic pay.
Standard settings
The standard SAP system contains a sample currency "USDN" which has five decimal places.
The default currency is derived from the

Change currency USD (2 decimals) by USDN (5 decimals)

Hi,
Please help me on below issue..
In SAP I use a company code with currency USD (currency with 2 decimals), I would like to chang USD by USDN (currency with 5 decimals).
how to make this change?
The SAP system is used for costing of products and is active.
What will become of the old cost calculations and prices stored in the purchasing info records?
Thanks in advance for answers
Jean-Marc

Hi
The changes can be made in transaction SU01 -> tab 'defaults' -> decimal notation.
Note: Functionality available in the transaction code OY04, but SAP does not recommend changing the decimals of the currency in the live system after implementation. So please consult with your finance team before doing any changes.
http://help.sap.com/saphelp_nw04/helpdata/en/01/dc31f9ad6d2e4d852ad4b169a5197c/content.htm

USDN Currency issue - "COMPUTE_BCD_OVERFLOW" Dump

Hey Guyz & Gals,
Could any one of you please assist me with the below explained issue ?
The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW',
was not caught in procedure "CFAKTOR" "(FORM)", nor was it propagated
by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
An overflow was discovered in an ongoing arithmetical operation with
operands of type P. Possible causes are:
1. The result field of type P is too small for the result.
2. The result or a intermediate result has more than 31 decimal places.
Information on where terminated :
Termination occurred in the ABAP program "RFKOPR10" - in "CFAKTOR".
The main program was "RFKOPR10 ". In the source code you have the
termination point in line 2664 of the (Include) program "RFKOPR10".
The termination is caused because
exception "CX_SY_ARITHMETIC_OVERFLOW" occurred in
procedure "CFAKTOR" "(FORM)", but it was neither handled locally nor
declared in the RAISING clause of its signature.
The procedure is in program "RFKOPR10 "; its source code begins in line
2655 of the (Include program "RFKOPR10 ".
Not only transaction -> S_ALR_87012178, but also lots of standard programs like
Vendor Ageing Analysis, Customer/Vendor account statements are giving
same kind of Short dumps.
This company code is using a 5 decimals currency. If I try to make it 2
decimals, then i am not getting short dump. We have also maintained table TCURX in OY03 & OY04.
But, as a business requirement 5 decimal currency is a must.
Please advice what to do ???????
Edited by: The Fuhrer on Dec 21, 2008 12:14 PM

If this is an unmodified SAP program, the forum really cannot help you. Look for notes and if you don't find any, raise an OSS message.
Rob

Problem with decimal in Japan currency

Hi Gurus,
I have a problem with Japan currency that when When i take the printout of document with JPY 5,168,277 it is wrongly printing as 51,682.77 but in document display it is showing correclty as 5,168,277. But when i check this in BSEG table it was wrong updated as 51,682.77 (WRBTR field) i hope it is picking the amount from this field for printing .
For the above i made changes in OY01 but i find there was no use.
In OY01 the decimal place setting is 1,234,567.89 the middle one of the three.
When i post the same amount to japan co code in currency JPY and if i check in BSEG table
Amount in LC                                      51,682.77
Amount          (WRBTR)                       51,682.77
Orig.reduction                                      0.00
G/L amount                                         5,168,277
When i post the same amount in non japan co code in JPY Currency and check in BSEG(area where i am facing problem)
Amount in LC                                      47,550.22
Amount          (WRBTR)                       51,682.77
Orig.reduction                                      0.00
G/L amount                                         5,168,277
Please tell me how to correct this.

May ne u can check this OSS note also 137626
Summary
Symptom
1. Which currencies have to be defined separately with regard to the number of decimal places?
2. What do I need to observe when maintaining decimal places for currencies?
3. Which Customizing presettings does SAP deliver in table TCURX (decimal places for currency codes)?
4. Does SAP deliver the Customizing presettings of decimal places for currency codes (Table TCURX) for upgrade installations?
5. Which information does SAP use for the specification of these Customizing presettings?
Solution
1. question: Which currencies have to be defined separately with
            regard to the number of decimal places?
Answer:
The number of decimal places can vary for currencies. Currencies which do not have two decimal places must be defined in table TCURX (decimal places for currency codes).
You can maintain this table via the R/3 Implementation Guide (Global Settings -> Currencies, Transaction OY04).
If a currency is not defined in Table TCURX (decimal places for currency codes), this currency is regarded as currency with two decimal places.
2. question: What do I need to observe when maintaining decimal places
            for currencies?
Answer:
During operation, you must neither delete currencies used nor change their definition of decimal places. Amounts in posted documents could become invalid or incorrect as a result.
3. question: Which Customizing presettings does SAP deliver in table
            TCURX (decimal places for currency codes) ?
Answer
At present, SAP delivers the following Customizing presettings for table TCURX:
ISO Currency Decimal places
Code
ADP   Andoran Peseta                            0
AFA   Afghani Afghani                          0
BEF   Belgian franc                             0
BHD   Bahraini dinar                            3
BIF   Burundi franc                             0
BYB   Belorussian rubel (old)                   0
BYR   Belorussian rubel (new)                   0
CLP   Chilean peso                              0
COP   Columbian peso                            0
DEM3 (Internal) German Mark (3 Dec.)           3
DJF   Djibouti franc                            0
ECS   Ecuadorian sucre                          0
ESP   Spanish peseta                            0
GNF   Guinea franc                              0
GRD   Greek drachma                             0
HUF   Hungarian forint                          0
IDR   Indonesian rupiah                         0
IQD   Iraqui dinar                              3
ITL   Italian lira                              0
JOD   Jordan dinar                              3
JPY   Japanese yen                              0
KMF   Comoros franc                             0
KRW   South Korean won                          0
KWD   Kuwaiti dinar                             3
LAK   Laos new kip                              0
LUF   Luxembourg franc                          0
LYD   Libyan dinar                              3
MGF   Madagascan franc                          0
MZM   Mozambique metical                        0
OMR   Omani rial                                3
PTE   Portugese escudo                          0
PYG   Paraguay guarani                          0
ROL   Roumanian Lei                             0
RWF   Rwanda franc                              0
TJR   Tadzhikistani rubel                       0
TMM   Turkmenistani manat                       0
TND   Tunesian dinar                            3
TPE   Timor escudo                              0
TRL   Turkish lira                              0
TWD   New Taiwan dollar                         0
UGX   Uganda shilling                           0
USDN (Internal) US Dollar (5 dec.pl.)          5
VND   Vietnamese dong                           0
VUV   Vanuata vatu                              0
XAF   CFA Franc BEAC                            0
XOF   CFA Franc BCEAO                           0
XPF   CFP Franc                                 0
4. question: Does SAP deliver the Customizing presettings of decimal
            places for currency codes (Table TCURX) for upgrade
             installations?
Antwort
Table TCURX (decimal places for currency codes) is a client-independent table of the delivery class "C" (Customizing table). Therefore the table contents for this table can only be delivered with new installations.
For upgrade installations, new or changed contents of Table TCURX are not delivered.
5. question: Which information does SAP use for the specification of
             these Customizing presettings?
Answer
Currency codes and decimal places for currency codes are defined in ISO standard 4217. For the specification of decimal places for currency codes, SAP uses this ISO standard.
For some currencies, for example, for the "Turkish lira", the decimal places which are used in reality deviate from the ISO definition. In many of these cases, SAP decided to adhere to the definitions generally used.
Example:
ISO standard 4217 defines two decimal places for the Turkish lira (TRL), however in reality zero decimal places are being used for the Turkish lira. SAP delivers zero decimal places as Customizing presetting for "Turkish lira".
Header Data
Release Status: Released for Customer
Released on: 14.08.2007 13:12:09
Priority: Recommendations/additional info
Category: FAQ
Primary Component: XX-CSC-XX Country specific Customizing & Functionality (Standard R/3)
Secondary Components: FI Financial Accounting
Releases
Release Independant
Related Notes
434349 - Change of decimal places of currencies
126531 - Collective note preliminary availability Colombia
Print Selected Notes (PDF)

Condition value currency based on amount currency in sales order creation

Hi all,
I have a requirement where during creation of a sales order with line items in the conditions tab where if condition type is EDI2 the amount currency should be USDN and accordingly condition value currency should also be changed to USDN.
I found the exit to acheive this and succeeded in changing the amount currency to USDN but condition value currency is also changing but for all above condition types.
I am using form userexit_field_modific_kzwi.
loop at xkomv where kschl = 'EDI2'.
XKOMV-WAERS = 'USDN'.
MODIFY XKOMV INDEX SY-TABIX TRANSPORTING WAERS .
select single waers into komk-waerk from TCURC where waers = xkomv-waers.
endloop.
Thanks & Regards
Jerry

Hi Vindo,
Thank you for your replay.
There is no Net value column in pricing procedure. Am able to change the Net value in the condtion tab of Item level but the problem is , the change is not reflected in condition tab of sales order header net value.This is creating a problem when we try to post the invoice document .
Cheers,
sravan.
Edited by: Rob Burbank on May 7, 2010 4:30 PM

Decimal change in currencies

Hi,
We have an issue related to our SAP Production system.
At the time of raising Billing invoices to customers in USD currency,
we are using currency SAR with two decimal places currently. Now our requirement is to bring three decimal places to USD currency for another project. new project also in the same lanscape .To proceed further i need to achieve this change in existing settings and test the impacts. so it is a cross client change (oy04)it will be seriously effected to our production system. Whether it will be suggested for changing the TCURX table? as these change is a urgent requirement for our new IS Oil
project, as in the SAP note : 434349 and 137626 it is clearly mentioned that it will affect the already posted documents , I need to know what are the other impacts and is there any other way to do the same.
Regards
Sanj

Hi sanj,
Check the table TCURX.Based on user profile you can get the currency format from USR01.Use This Code: It takes care of decimal notation based on user profile.What ever may be the user profile for decimal notation.
Expl:
FIELD_NUM = 1,233.50 And You can maintain this table via the R/3 Implementation Guide (Global Settings -> Currencies, Transaction OY04). If a currency is not defined in Table TCURX (decimal places for currency codes), this currency is regarded as currency with two decimal places.
Exp:ISO Currency Decimal places Code- USDN (Internal) US Dollar (5 dec.pl.) 5 ( OR )
Table TCURX (decimal places for currency codes) is a client-independent table of the delivery class "C" (Customizing table). Therefore the table contents for this table can only be delivered with new installations.
For upgrade installations, new or changed contents of Table TCURX are not delivered.
Currency codes and decimal places for currency codes are defined in ISO standard 4217. For the specification of decimal places for currency codes, SAP uses this ISO standard.
For some currencies, for example, for the "Turkish lira", the decimal places which are used in reality deviate from the ISO definition. In many of these cases, SAP decided to adhere to the definitions generally used.
Exp:ISO standard 4217 defines two decimal places for the Turkish lira (TRL), however in reality zero decimal places are being used for the Turkish lira. SAP delivers zero decimal places as Customizing presetting for "Turkish lira".
Regards
Sridhar
Edited by: sridhar.shetty on Feb 21, 2012 7:18 AM

Currency Translation on Key Date for AR Aging

Need your valuable advice!
I have created an AR Aging query including both Open and Cleared Items based on 0FIAR_C03_Q0005 standard query. However the requirement is to do currency translation to Group Currency (USD) on Key Date. This Key date is defaulted to today but the user can change this to go back in time and pull all the ARs as of that back dated key date.
I was planning to create a currency translation type on M rate based on the Key Date Variable in RSCUR. However I am confused on which variable to base this currency translation. I have several key date variables in my query such as 0P_KEYD2 (based on Posting Date), 0P_KEYDT (based on Net Due Date) and 0P_KEYD3 (based on Clearing Date).
Which Key Date Variable should I use in 'Time Reference from Variable' field in RSCUR? Would it be one of the 3 mentioned above or something else and why?
Appreciate your valuable advice.
Thanks,
Al

Hi,
Yes I do want to use the Key date from the variable screen and I am using the standard 0FIAR_C03_Q005 with slight modification including currency translation.
As I mentioned in my original post I have several key date variables in this query such as 0P_KEYD2 (based on Posting Date), 0P_KEYDT (based on Net Due Date) and 0P_KEYD3 (based on Clearing Date). My question is which one should I use if I want to base it on the specific key date variable from the variable screen? I need the specific Key Date variable technical name.
Thanks,
Al

CURRENCY (USDN)

Similar Messages

Maybe you are looking for