Tax conversion during Intercompany EDI (RD04 output)

We have a situation where there is an intercompany billing from company A to B - both of them are in different countries and hence follow different tax codes.   The RD04 output posts the AP document in company code B with a different tax code.    We have checked OBCD, and this does not carry any relevent config.    What else governs this conversion ?
Many thanks,
Sanker

Hi E_Hinojos and all,
I went to CUNI again and under ALE/EDI, the field was already populated with EA. The solution was that I just need to check the "Primary" box under that field and the error message went away.
Now, I'm getting a new error message after simulating the IDOC again in WE19:
IDoc number            0000000000198023
Direction              2     Inbound
Status                 51    Application document not posted
G/L account 191100 requires a valid tax code
Message no. FS214
Diagnosis
The master record of account 191100 requires you to enter a valid tax code in each item for this account in company code 0001.
System Response
Error message
Procedure
Enter a valid tax code.
I've already maintain transaction OBCD with input tax codes but I'm not sure whether I did it correctly. I'd like to know how the system would know which tax code to take or choose from OBCD table? The GL 191100 under transaction FS00 allows input tax codes only.
Any suggestion would be appreciated.
Thanks.
Edited by: Steven Khoo on Feb 18, 2011 4:16 PM
Edited by: Steven Khoo on Feb 18, 2011 5:17 PM
Edited by: Steven Khoo on Feb 19, 2011 12:45 AM

Similar Messages

  • EDI Shipment Output  Master Data Conversion

    Hi,
    I am using LSMW to upload EDI Shipment Output Master Data into file can anyone suggest me any standard BAPI or Idoc avail for the same or any function module available to do this.
    Thanks
    Dhirendra

    we have below  LSMW IDOC methods
    OILSHL                          TD Shipment to TAS
    RECSHP                          Recommended shipments
    SHIPMENT_CREATEFROMDATA         Create shipment
    SHIPPL                          Inbound planned shipments
    SHPMNT_TNDR                     Shipment tendering
    TPSSHT                          Shipping planning system: Transfer planned shi

  • Intercompany Billing using RD04 Output

    Hi,
    We are using RD04 successfully to post incoming AP invoices. We have the timing for RD04 set to '4'.
    However, we have a problem when the original invoice is not released to accounting if there is some error. In this case we don't want the system to process the RD04 output.
    In other words, I would really like it if someone could let me know how I can make 'successful release to accounting' (VBRK-RFBSK=C) a pre-requisite to processing RD04.
    Thanks,
    Anisha

    Hi Anisha,
    Go to V/40 (Output types for Billing)
    Select your output type RD04 and check the Access sequence assigned to it.
    It might be "0004". Copy this access sequence into "Z004"  access sequence  and in this Z004 access enter the requirement as "62". This requirement routine will validate the entire billing document and also verify whether the data has been passed to accounting.  
                 Assign the new Access sequence to your output type.
              I don't recommend you to change the RD04, Its better to copy the RD04 into custom output type like "ZD04" and assign the access sequence to it.
    Now new output will be triggered only after the billing document was save properly and data been passed to accounting.
    Hope this gives you clear idea.
    Regards,
    Ajai.
    Don't forget to reward points if helpful.
    null

  • Could you pls give the details about the Unicode conversion during Upgrade

    Hi,
    Can anyone give details about the Unicode conversion during SAP Upgradation fro 4.6C to ECC6.
    Waiting for quick response
    Best Regards,
    Padhy

    Hi,
    These are the few points i gathered during my upgradation project.
    Before starting any upgradation project, it is necessary to take up the back-up of the existing systems. As we are going to upgrade the entire system, we will be changing so many things and if something happens, without back-up, we will be in a trouble.
    So it is advised to keep a back-up of the existing system.
    Say for example we have the existing system E4B which is of Version 4.6C. Now we want to upgrade it to Version 4.7. Let us see how we can do it.
    Version upgrades not only means that we need to run the new Version CD over the existing Version System but only involves some other thing.
    Version Upgrade involves the following Steps.
    Say we want to upgrade for Version 4.7 from Version 4.6, which is in the System E4B. Now we created one more system called as E1B in which the upgradation for Version 4.7 can be done.
    • First copy the entire E4B system into the E1B System which is created for Version 4.7.
    • Apply the Version 4.7 CD provided by SAP over the E1B System.
    • Now check whether all the functionalities that was in E4B system works fine with E1B system also.
    Thus the Version Upgrade involves two steps.
    1. SAP Upgradation with the help of the CD
    2. Manual Upgradation.
    1. SAP Upgradation with the help of the CD
    This is nothing but after taking the copy of the existing system into a new system, the upgradation CD from SAP is applied over the new system.
    2. Manual Upgradation.
    This Manual Upgradation involves
    2.1 Upgradation of Standard Objects
    2.1.1 SPAU Objects
    2.1.2 SPDD Objects
    2.2 Upgradation of Custom Objects.
    Upgradation of Custom Objects can be placed under the following three categories.
    Unicode Compliance
    Retrofit
    Upgrade
    Please Find below some of the common Unicode Errors and their solutions
    1. Error:
    In case of Translate Error; ‘Dangerous use of Translate in Multilingual system.’
    Correction:
    To correct the Error occurring on TRANSLATE statement – use this additional statement before the Translate statement.
    SET LOCALE LANGUAGE sy-langu.
    This statement defines the Text Environment of all the programs & internal sessions in the language specified in the LANGUAGE KEY, which in this case is “sy-langu”, i.e. the log on language of the user.
    2. Error:
    In case of Open Dataset Error; ‘Encoding Addition must be included.’
    Correction:
    This Error occurs only when the MODE is TEXT.
    To correct the Error occurring on OPEN DATASET statement – use this statement instead.
    OPEN DATASET dataset_name FOR access IN TEXT MODE ENCODING DEFAULT.
    Where: dataset_name – NAME OF THE DATASET.
    Access – INPUT or OUTPUT or APPENDING or UPDATE.
    DEFAULT - Corresponds to UTF-8 in UNICODE systems &
    NON_UNICODE in NON-UNICODE systems.
    3. Error:
    In case of the usage of the Obsolete FM UPLOAD/DOWNLOAD or WS_UPLOAD/DOWNLOAD; ‘Function module UPLOAD is flagged as obsolete.’
    Correction:
    The FM GUI_DOWNLOAD/UPLOAD is used.
    The variations to be made in the parameters of the FM:
    1. Filename – It must be of STRING type.
    2. Filetype – “DAT” is not used any longer, instead “ASC” is used.
    3. Field Separator – The default value “SPACE” is used, incase for a TAB separated file “X” can be used.
    4. Error:
    In case of CURRENCY/UNIT Addition Error; ‘Use addition CURRENCY/UNIT when outputting.’
    Correction:
    The CURRENCY addition specifies the currency-dependant decimal places for the output of the data objects of type i or p. To obtain the currency-key, the field CURRKEY of the table TCURX is used. The system determines the number of the decimal places from the field CURRDEC of the selected CURRKEY.
    To correct this error follow the following method:
    WRITE: /3 'TOTAL',' ', TOTAL.
    WRITE: /3 ‘TOTAL’,’ ‘, TOTAL CURRENCY ‘2’. --- Where ‘2’is the Currency Key for Getting 2 decimal places.
    5. Error:
    In case of TYPE X Error; ‘Variable must be of C, N, D, T or STRING type.’
    Correction:
    We need to change all the Type X (Hexadecimal) variables to Type C with their values unchanged.
    So the method to be followed is:-
    1. Load the definition of the class CL_ABAP_CONV_IN_CE or CL_ABAP_CHAR_UTILITIES.
    2. Declare the variable as Type C, and use the method UCCP(‘XXXX’) of the class CL_ABAP_CONV_IN_CE where XXXX represents the 8-bit Hexadecimal value and incase the variable holds a Hex value for a Horizontal Tab , then the Attribute “HORIZONTAL_TAB” of the class CL_ABAP_CHAR_UTILITIES can be used directly instead of using the method UCCP.
    E.g.:
    i) *DATA: TAB TYPE X VALUE 09, “Tab character
    CLASS: CL_ABAP_CHAR_UTILITIES DEFINITION LOAD.
    DATA TAB TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
    ii) * DATA: CHAR TYPE X VALUE 160.
    CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
    DATA CHAR TYPE C.
    CHAR = CL_ABAP_CONV_IN_CE=>UCCP(‘00AO’).
    (Here ‘00A0’ is the Hexadecimal equivalent of the decimal 160).
    3. Incase the TYPE X Variable has a length more than 1, then an internal table must be created for the variable.
    E.g.:
    CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
    DATA : LF(2) TYPE X VALUE 'F5CD'.
    DATA : BEGIN OF LF,
    A1 TYPE C,
    A2 TYPE C,
    END OF LF.
    LF-A1 = CL_ABAP_CONV_IN_CE=>UCCP('00F5').
    LF-A2 = CL_ABAP_CONV_IN_CE=>UCCP('00CD').
    6. Error:
    In case of the Character “-“Error; ‘The Character “-“can’t appear in names in Unicode Programs.’
    Correction:
    The Character “-“(Hyphen) appearing in Variable names is replaced by the character “_” (Under Score) for Unicode/Upgrade Compliance.
    E.g.:
    *wk-belnr LIKE bkpf-belnr,
    *wk-xblnr LIKE bkpf-xblnr,
    *wk-date LIKE sy-datum,
    *wk-wrbtr LIKE bseg-wrbtr,
    *wk-name1 LIKE lfa1-name1,
    *wk-voucher(8) TYPE c.
    wk_belnr LIKE bkpf-belnr,
    wk_xblnr LIKE bkpf-xblnr,
    wk_date LIKE sy-datum,
    wk_wrbtr LIKE bseg-wrbtr,
    wk_name1 LIKE lfa1-name1,
    wk_voucher(8) TYPE c.
    7. Error:
    In case of The SUBMIT-TO-SAP-SPOOL Error; ‘you should not use the statement SUBMIT-TO-SAP-SPOOL without the WITHOUT SPOOL DYNPRO addition. ‘
    Correction:
    1. Declare variables of type PRI_PARAMS, ARC_PARAMS, and a variable of TYPE C which would be used as a VALID FLAG.
    2. Call the FM GET_PRINT_PARAMETERS:
    CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
    ARCHIVE_MODE = '3'
    DESTINATION = P_DEST
    IMMEDIATELY = 'X'
    IMPORTING
    OUT_ARCHIVE_PARAMETERS = archive_parameters
    OUT_PARAMETERS = print_parameters
    VALID = valid_flag
    EXCEPTIONS
    INVALID_PRINT_PARAMS = 2
    OTHERS = 4
    3. Use the SUBMIT-TO-SAP-SPOOL statement.
    E.g.:
    •     submit zrppt500
    •     using selection-set 'AUTO3'
    •     with res_no eq lo_rsnum
    •     with sreserv in preserv
    •     to sap-spool destination p_dest
    •     immediately 'X'. "print immediate
    DATA: print_parameters type pri_params,
    archive_parameters type arc_params,
    valid_flag(1) type c.
    CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
    ARCHIVE_MODE = '3'
    DESTINATION = P_DEST
    IMMEDIATELY = 'X'
    IMPORTING
    OUT_ARCHIVE_PARAMETERS = archive_parameters
    OUT_PARAMETERS = print_parameters
    VALID = valid_flag
    EXCEPTIONS
    INVALID_PRINT_PARAMS = 2
    OTHERS = 4
    Submit zrppt500
    Using selection-set 'AUTO3'
    With res_no eq lo_rsnum
    with sreserv in preserv
    to sap-spool
    SPOOL PARAMETERS PRINT_PARAMETERS
    ARCHIVE PARAMETERS ARCHIVE_PARAMETERS
    WITHOUT SPOOL DYNPRO.
    8. Error:
    In case of Message Error; ‘Number of WITH fields and number of Place Holders are not same ‘.
    Correction:
    Split the statement after WITH into the same number as the place holder for that Message ID.
    E.g.:
    1. * MESSAGE E045.
    MESSAGE E045 WITH '' ''.
    2. in program ZIPI0801
    •     Start of change for ECC6
    •     message e398(00) with 'Could not find access sequence'
    •     'for condition type:'
    •     p_ptype.
    message e398(00) with 'Could not find '
    'access sequence'
    'for condition type:'
    p_ptype.
    •     End of change made for ECC6
    9. Error:
    In case of Move between 2 different Structures; ‘The structures are not mutually convertible in a Unicode program.’
    Correction:
    Make both the Data Types compatible and then assign the contents.
    E.g.:
    The statement –“move retainage_text to temp_text.” Gives an error, where RETAINAGE_TEXT is an internal table and TEMP_TEXT is a string of length 200.
    A Feasible solution for this is to specify from which position to which position of the string, the fields of RETAINAGE_TEXT should be assigned.
    TEMP_TEXT+0(1) = RETAINAGE_TEXT-DQ1.
    TEMP_TEXT+1(1) = RETAINAGE_TEXT-HEX.
    TEMP_TEXT+2(20) = RETAINAGE_TEXT-FILLER1.
    TEMP_TEXT+22(15) = RETAINAGE_TEXT-AMT_DUE.
    TEMP_TEXT+37(8) = RETAINAGE_TEXT-TEXT.
    TEMP_TEXT+45(10) = RETAINAGE_TEXT-DUE_DATE.
    TEMP_TEXT+55(1) = RETAINAGE_TEXT-DQ2.
    10. Error:
    In case of ‘no description found’; ‘add a GUI title’.
    Correction:
    In this type of error gui title is generally missing so add a GUI title to the module pool.
    11. Error:
    In case of ‘writing internal or transparent table’
    Correction:
    Write individual fields.
    E.g.:
    WRITE: / EXT. --> EXT should be a character type field
    WRITE: / EXT-ZZSTATE, EXT-LINE_NO, EXT-LINE_TXT, EXT-AMT, EXT-ZZSKUQTY.
    12. Error:
    In case of ‘combination reference table/field S541-UMMENGE does not exist’
    Correction:
    Was due to error in reference table S541. TABLE S541 has errors
    1)”Foreign key S541- ZZMARKET (ZZMARKET AND KATR2 point to different domains)”
    2)”Foreign key S541-ZZACQUIGRP (ZZACQUIGRP AND KATR8 point to different domains)”
    Changed the domain of ZZMARKET (from ZMKCODE to ATTR2)
    And that of ZMKCODE (from ZACCODE to ATTR8)
    13. Error:
    In case of ‘KEY does not exist’
    Correction:
    The reference table for field KBETR was KNOV earlier changed it to RV61A as KNOV was in turn referring to RV61A.
    14. Error:
    Incase of ‘WRITE’ statement, ‘Literals that take more than one line is not permitted in Unicode systems.’
    Correction: To correct this error, we need to align the spaces accordingly so that the statement doesn’t go beyond the line.
    15. Error:
    Incase of Data statement, ‘The data type ZWFHTML can be enhanced in any way. After a structure enhancement, this assignment or parameter might be syntactically incorrect………..’
    Correction: To correct this error, instead of “like” in the Data statement, use “type”.
    16. Error:
    Incase of DESCRIBE statement, ‘DESCRIBE can be used only with IN BYTE... Or IN CHARACTER mode in Unicode systems.’
    Correction: To correct this error, use additional text, IN BYTE MODE / IN CHARACTER MODE along with this statement.
    CHARACTER MODE is added when the data object is of flat/ character type.
    BYTE MODE is added when the data object is a deep structure.
    Syntax: DESCRIBE FIELD data_obj : LENGTH blen IN BYTE MODE,
    LENGTH clen IN CHARACTER MODE.
    Where blen and clen must be of type I.
    17. Error:
    Incase of DO-LOOP Error,’ In Do loop range addition needed‘
    Correction:
    An internal tables is declared and the two fields (VARYING field and NEXT field) were
    Included inside the internal table
    E.g.: In program SAPMZP02
    DO 11 TIMES
    •     VARYING STATION_STATE FROM STATION1 NEXT STATION2. “ECC6
    CASE SYST-INDEX.
    WHEN ‘1’
    STATION_STATE = STATION1.
    WHEN ‘2’
    STATION_STATE = STATION2.
    WHEN ‘3’
    STATION_STATE = STATION3.
    WHEN ‘4’
    STATION_STATE = STATION4.
    WHEN ‘5’
    STATION_STATE = STATION5.
    WHEN ‘6’
    STATION_STATE = STATION6.
    WHEN ‘7’
    STATION_STATE = STATION7.
    WHEN ‘8’
    STATION_STATE = STATION8.
    WHEN ‘9’
    STATION_STATE = STATION9.
    WHEN ‘10’
    STATION_STATE = STATION10.
    WHEN ‘11’
    STATION_STATE = STATION11.
    18. Error:
    Incase of the parameter QUEUE-ID Error,’ QUEUE-ID’ is neither a parameter nor a select option in program rsbdcbtc.’
    Correction:
    The parameter in program rsbdcbtc is QUEUE_ID and so is changed in this program
    E.g.: In program Z_CARRIER_EDI_INTERFACE
    •     submit rsbdcbtc with queue-id = apqi-qid and return. "ECC6
    •     The parameter name changed by replacing '-' with '_' as in program rsbdcbtc "ECC6
    Submit rsbdcbtc with queue_id = apqi-qid and return. "ECC6
    19. Error:
    Incase of EPC Error,’ Field symbol <TOT_FLD> is not assigned to a field ‘.
    Correction:
    This error couldn't be rectified as the error occurs in a Standard SAP include- LSVIMF29.
    The OS Note - 1036943 needs to be applied.
    Error:
    OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE.
    Correct:
    OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
    Error:
    Constants : c_tab type x value '09' .
    Correct:
    Constants : c_tab type abap_char1 value cl_abap_char_utilities=>horizontal_tab .
    Error:
    Data : begin of output_options occurs 0 . Include structure ssfcompop.
    Data : end of output_options .
    Correct:
    Data : output_options type standard table of ssfcompop with header line .
    Error:
    PARAMETERS : NAST TYPE NAST .
    Correct:
    PARAMETERS : NAST TYPE NAST NO-DISPLAY .
    Replace WS_DOWNLOAD and WS_UPLOAD by
    GUI_UPLOAD and GUI_DOWNLOAD and check the import and export parameter types , do the changes accordingly. Because FILENAME paramater type is different because of this it will give dump.
    For issue during Issue using SO_NEW_DOCUMENT_ATT_SEND_API1 Function module, the solution is After this FM we should put COMMIT WORK.
    Issue:
    Moving data from one structure to another structure if those two structures are not compatible
    Solution:
    we should use move-corresponding or field by filed we need to move it.
    If database structures are different in 4.6c and ECC6.0,
    Then we should go with append structure concept.
    While testing the report if it gives dump at Select query level or any database or view level,then just goto that table or view and goto the data base utility(se14) adjust the database. But make sure that selected radio button in se14 transaction should be activate and adjust database
    Also Check this link.
    http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/frameset.htm
    Reward points if helpful.
    Regards,
    Ramya

  • Account determination error during intercompany billing invoice

    Hi experts,
    I am getting 'Account Determination Error' shows in red during 'intercompany' billing.
    I tried to release to accounting but didn't help.
    Pls advise
    Br,
    Umesh

    Hi Sushant,
    The error during the invoice creation. This document is for intercompany billing.
    I checked in Account Determination Analysis --> Revenue Accounts
    When I click on the Item no., it shows as 'No G/L account found in KOFI' & messege 121.
    In VKOA, there are few tables but I am not sure how & what to compare between these two.
    Br,
    Umesh

  • EDI billing outputs are capturing credit memos as well as invoices

    I am a newcomer to the company I am currently with, and to this forum, and I have 6 years of experience in EDI and SAP SD.
    I am working on a project to determine why our EDI billing outputs are capturing credit memos as well as invoices, and attempting to send them by EDI, causing failures in our Seeburger translator.  Most customers donu2019t want credit memos by EDI. My goal is to track backwards and determine what portion of the EDI process in SAP is pulling credit memos rather than just invoices.  I suspect that someone intentionally made changes in the past to put this in place, but we need to have a message type that includes invoices and credit memos, to be attached to specific partners that want this, and another more standard message type that sends only invoices. 
    The message control for the example partner specifies Message Type ZURH (customized by this company for some reason), Application V3 (which seems standard), and process code SD09 (which seems standard).  Could someone help me to navigate to an area where I may be able to find out what parameters are used to determine what transaction types are pulled to be sent out by EDI for billing?  I suspect that the issue may be in Application V3, but I am unable to find any help to view u2018Applicationsu2019, because application is such a widely used word. 
    How can I display/change Application V3, in order to check itu2019s contents?
    Any other ideas why credit memos may be included would be appreciated, and I always appreciate having the transaction codes mentioned as well.
    Thank you in advance for your assistance. 
    Application V3 (what specifies what transaction type this pulls?)
    Message Type ZURH,
    Process Code SD09.
    Access Sequence used is ZSD1 Billing Documents (Access Sequence ZSD1 does not appear in transaction V/48 (?))
    Transmission Medium is 6 EDI.
    The program is RSNASTED, and the FORM Routine is EDI_PROCESSING.

    Satish,
    Thanks for the suggestions.
    I checked transaction VV33 u201CDisplay Output Condition Records: Billingu201D for Output Type ZURH, Key Combination Sales Org/Payer, and I find the example customer  linked to ZURH, as I would expect (5010013645     BEST BUY CANADA  Vendor #41448     PY          6     1). 
    I donu2019t see any data about specific transaction types such as credit memos or invoices, so I may not be looking in the right place.  I donu2019t find entries under any other key combination.  How would I check if Output Condition records are maintained for credit memos?
    In regards to the output type being assigned to the credit memo billing type (ZG2U), Iu2019m afraid I donu2019t know how to check that either. 
    In NACE, I see that u2018Proceduresu2019 list the CTyp (?), and procedure US0001 is the only one that includes credits and debits. I donu2019t recognize the Ctyps ZDN0 and ZCN0. The billing type is ZG2U, which I don't see in any of the Procedures:
    10     1     RD00     Invoice
    20     2     ZPRO     Proforma Invoice
    30     1     ZCAN     Canadian Cust. Inv
    40     1     ZCOM     Commercial Invoice
    50     1     ZDN0     Debit Note
    60     1     ZCN0     Credit Note
    How would I be able tell which u2018Procedureu2019 is being used for Application V3, and how would I change that to another Procedure for testing?

  • My 5 keeps pausing conversations during a call, how can I get it to lock

    My cheek or ear always mutes the conversation during a call. Is there a way to get it to auto lock during a call?

    It sounds like you have a problem with the proximity sensor that turns the screen off when you are on the phone. Do you have a case on the phone? If you do, try taking the case off and test a call. See if the screen turns off when you bring the phone up to your ear. If it does, it is possible the case is blocking something in the proximity sensor which is not allowing it to work properly. If it still does not work after taking the case off, you can perform the user troubleshooting, power off/on, reset by holding the sleep/wake and home buttons together until you see the Apple logo and then release. If that doesn't work, then a restore, first from a backup and if needed then as a new device if necessary.

  • EDI Message output gets processed for held PO

    Hi All,
    When I save my purchase order as a HELD PO (EKKO-MEMORY=X), EDI Message output gets processed.
    Can you please provide me any inputs to disable this.
    Regards
    Deepak

    Hi All,
    Can anyone provide any inputs on this.
    Regards
    Deepak

  • WTMG withholding tax conversion

    Hello to you all,
    Once I run Tcode WTMG withholding tax conversion,
    I was surprised to receive an error message FWTM379 "Table T059Z,
    country IL, percentage rate for type 06, code 01 (==> long txt)".
    The classic WT codes based on the idea that the percentage maintained 
    within the code itself, different codes for every percentage rate.
    The extended WT codes contain maximum percentage per code and the
    percentage is maintained within the vendor master record itself.
    Based on the different idea, how can we assign the classic withholding
    tax codes to the withholding tax types and codes for extended
    withholding tax and have the exact percentage (without creating the all
    old codes again just as a new one)?
    Regards,
    Yoav

    Hi Yossi,
    Please check SAP NOTE:186989 - Changeover withholding tax
    Hope this will help you.
    Regards
    Eugene

  • Value conversion during syndication.

    Hi All,
    I need to do a value conversion during syndication of records out of MDM. The values maintained in my MDM Repository is true and false while the destination system can only read Y and N. What would be the best option to have this value conversion done during the auto syndication?
    Appreciate your responses.
    - Aditya

    One way to handle this is by using key mapping on a lookup table instead of a boolean field.  Often times your remote systems will have different internal values than the ones you are storing in your system.  For example, you may store "True" or "False" as values in your MDM repository, however ECC doesn't accept those values, instead it wants "X" or "NULL".  Likewise, a third-party system may expect "T" or "F".  The same thing goes for other fields in your repository (ie: country codes, region values, etc).  In cases such as this, you should create a lookup table with key mapping enabled.  Then, you can maintain different values based on the remote system.  In other words, you may store the value "TRUE" in your lookup table, but the key mapping for true may maintain "X" for ECC and "T" for a legacy system that you define in the console.  Then, when you build your syndication map, you may the remote key to the destination field instead of mapping the actual code value of your repository.  This way the correct value will always get syndicated to the partner system regardless of what system is being syndicated to.
    Does that make sense?

  • Capturing service tax categories during FB60/MIRO

    Hi
    This is with reference to the service tax categories, which is required during monthly return in India.
    To the best of my knowledge, SAP does not have any standard solution to capture these servie tax categories during transaction entry till date.
    There are almost 102 categories defined by Govt of India for different kind of services. These categories are need to cature during transaction and will used later in filling return.
    I am trying to find a filed which is available in FB60/MIRO and FBL3N so that what transaction recorded in service tax payble GL, will have trace of services.
    Please suggest which filed i should use in FB60 or MIRO, which will have F4 help and also appear in FBL3N.
    Please reply.
    Regards
    DD

    Hi DD,
    We have solved a similar problem using text keys. Under SPRO GL Accounting -> Business transactions -> GL Account postings -> Carry out and check document settings -> Define texts for line items, define keys for service tax categories like ST1, ST2 with descriptions. These can be selected from F4 help and entered by the user during invoice entry. You can see them in FBL3N, filter and sub-total it.
    Regards
    Sharabh

  • EDI msg output

    Hi
    We are with SRM 5.0 and Classic Scenario.
    While testing the whole scneario in our quality system, from SC creation to PO creation, we need to set EDI message output.
    Can anyone explain where it can be done ?
    Thank you
    Maron

    If you need to send the PO you need to configure output control and an outbound partner profile in WE20. The partner profile is for the vendor or customer, the message and basic type, and extension if the IDoc has been extended.
    In the Message Control tabe of the outbound partner profile, you'll add the following line:
    Application = EF, Message Type = NEU and Process Code = ME10.
    NEU is the standard message type for generating output from PO's. It's already set up to create IDocs.
    But you also need to make an entry into an output control table using transaction MN04 or MN05. This entry links your document to a number of different potential parameters that are used to identify the type of output that needs to be generated. It's as the same as setting up your documents to print.
    But at this point I can't help you more because I don't know your system or your data. You need to get with your functional consultant to show you what you need to do to create the output record. They may also want to create a custom message type for your PO. You need to work it out with them.
    Without this table entry made thru MN04 or MN05, the IDoc won't come out.
    Good luck.

  • Erroe with Tax amount conversion during PO creation

    Hi,
    I am getting the following error while PO creation. I have already searched for existing threads and have also maintained entry in OB08 but the error still exists.
    *Enter rate EUR / INR rate type  for 20.01.2012 in the system settings
    Message no. SG105
    Diagnosis
    For the conversion of an amount into another currency, an entry is missing in the currency conversion table.
    Procedure
    Add the missing entry in the currency conversion table.
    Execute function
    You can then continue to process the commercial transaction.*
    I have two concerns here:  1. the error is not showing any exchange rate type, and   2. at header level of PO it is by default picking some conversion rate which is not maintained in ob08.
    Thanking in anticiaption.
    Regards,
    Nikhil

    Dear,
    Are you creating PO for Imports? if yes then please check the following;
    SPRO>IMG>Logistics General>Tax on Goods Movement>India>Basic Settings>Maintain Company Code Settings...please check what is the exchange rate type for CVD is maintained. If it is different from "M" then please maintain the tax rate for this exchange rate type...
    Hope this helps!!
    Br,Vivek

  • Tax Code in Intercompany Billing

    Hi Gurus,
    I am creating an intecompany billing document, both the countires are different. I have three accesses in output tax condition. 1. Domestic, 2. Exports, 3. Dep country / Dest Country.
    Let us say the intercompany sales is between Germany DE  and UK, but the system is only picking up the domestic tax which is setup in MWST for country DE. My requirement is, the system should pick up the condition record mainained for the last access Dep country / Dest country.
    Note: We don't have any record maintinaed for 2. Exports, we are not using it.
    Please give your ideas.
    Regards,
    Prasanth

    Dear Prasanth
    As you would be aware in Access Sequence V/07, system will give first preference to step number and then only the "Exclusive" check box.  So why dont you insert the table 78  (Departure Country / Destination Country)  above to table 2  (Domestic Taxes)  and retry ??
    thanks
    G. Lakshmipathi

  • Intercompany EDI processing

    Hi,
    Dear all in my inter company I assigned out put type RD04 and partner profile is maintain for both outbound and inbound processing when I save then it process properly and give IDOC number
    But when try to check status with WE02 it shows error as
    A company code cannot be determined for LI 0000050100
    Message no. FD006
    Diagnosis
    The system cannot determine the relevant company code since the allocation of the data transferred in the invoice is missing in Financial Accounting customizing.
    The company code can be determined outside of the system and be put into the intermediate document (for example, from the EDI subsystem). Then the company code must be put into the E1EDK14 segment and ORGID field and the value "011" used as the qualifier.
    Procedure
    Determine the company code for LI 0000050100  in Financial Accounting customizing.
    Also I had maintained copany code data where i asigned partner type LI >> VENDOR CODE >> comapny name >> CoCode
    But still facing error
    Where as when read help on this it state that if you determining data from outside system from E1EDK14 & value 011 and also if you maintained in SD intercompany billing >> Automatic Posting To Vendor Account (SAP-EDI)
    THEN YOU NEED NOT TO MAINTAIN IN FI
    When I removed from SD then out put is not excepting in invoice give error maintain partner profile for EDI
    What is missing out ???
    Kapil

    Hi,
    Here I found that support package for SAP_APPL should be SAPKH60016
    Where as in my system it is
    SAP_APPL     - 600   -     0007     - SAPKH60007     - Logistics and Accounting
    If my basis apply correction note will it become up to 16 ?????????????
    Kapil

Maybe you are looking for