Portugal - Fiscal Maps immobilized

olá we are with problems in the fiscal maps of immobilized for Portugal, basically the information leaves changed, what it would have to be in map 33,11 is in map 33,12, the groups that we have had badly been all reevaluated and the problem is in the admission of the date of reevaluation therefore the exchange of the fiscal maps. somebody had similar problem?

Hi - One thing you can try to sort this out is the following.
On your memory card, make a backup of the following two folders onto your PC first BEFORE DOING ANYTHING ELSE, but delete the "cities" and "private" folders on the memory card in your phone. They will be hidden so ensure you have "show hidden files and folders" ticked in Windows Explorer.
Then load Nokia Maps again - it should load correctly.
Wait for it to get a lock and download the Maps whilst it is running for the area you are in either via WiFi or your network operator.
Once complete, quit the application and use MapLoader to download the maps for Portugal onto your memory card for ease of use.
Once complete try doing a search for your town in question.
Please let me know how you get on.
Regards,
Edward

Similar Messages

CHANGE OVER FROM TAXINJ TO TAXINN

HI ALL ,
TAXINJ and TAXINN cannot co exist in the same system.
If you are talking about technical Upgrade, then I don't think this would be feasible since old Txn would have got posted with TAXINJ procedure with rates as defined in Tax codes and now after migration to TAXINN in same box, the system would pick value from Condition records.
Just check this basic point of feasibility before we go ahead and look for changes.
In SuN the change is for existing implementation, here at present they have R/3 4.7, and are now in the process of technical upgrade to ECC 6.00; TAXINN is required to be implemented in the upgraded version.
At present they are using around 129 pricing procedures, 25 sales org,220 tax codes in TAXINJ. Suzlon has 21 company codes, 219 plants and 1300 end users the whole nature of group activities results in use of all possible types of indirect taxes in India like VAT, CST, Excise, Service Tax etc...
i have tried to search on sap help, service market place and others but could not come across any document for the change over. However i will try again.
what are the things i need to take care before any implications busisneww point of view, what will be the status of open sales order and purchase orders, and splitting delivery docs. which are under process, what will be the cutoverstrategy.
need ur help and guidance, thanks in advance.
We are migrating from 4.7 to ECC 6.00 ( technical upgrade only), at the same time we will shift from TAXINJ to TAXINN,please let us know the steps requred to do this activity.
RELEASE NOTES OR OSSNOTES, ANY DOCUMENT STEP BY STEP IS REQUIRED asap.
CHEERS
SRI_CNU

Hi
Vasu Sri,
I got this document from some body might help u a bit.
Condition-Based Excise Determination in MM (New)
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system can calculate excise duties
and sales tax in Materials Management (MM) using the standard condition technique.
SAP has enhanced the existing tax procedure, TAXINJ, so that it now supports formula-based
and condition-based excise determination. The R/3 System also comes with a new tax procedure,
TAXINN, which only handles condition-based excise determination.
Which Tax Procedure Must I Use?
Existing customers must continue to work using the same tax procedure.
If you switch to a new tax procedure, you cannot display any documents that you have already
posted using the old tax procedure.
If you have worked with formula-based excise determination in previous releases and wish to
continue, you do not have to do anything. However, if you wish to start using the
condition-based excise determination method, proceed as specified below.
We recommend that new customers use the condition-based excise determination and tax
procedure TAXINN.
<b>How Do the New Functions Work?</b>
First, customize the system in the activities listed below. Then, for each material, create one
condition record for each form of excise duty and sales tax that applies, and enter the tax code
for purchasing documents (see below) in every condition record.
When you come to create a purchase order, enter the tax code in each line item. The tax code
tells the system whether to look in the condition types for formula-based or condition-based
excise determination
To set up the new excise determination method, carry out the following activities:
IMG activity
What to do
Check Calculation Procedure
Existing customers: Adjust your tax procedure to
match the changes to TAXINJ. Steps 560-583 are new, as are 593-598.
New customers: Create a copy of TAXINN.
Select Tax Calculation Procedure
New customers only: Assign the copy of
TAXINN to India.
Maintain Excise Defaults
New customers only: Enter the condition type
that you use for countervailing duty.
Define Tax Code for Purchasing Documents
Define a tax code.
Assign Tax Code to Company Codes
Assign the tax code to the company codes that it
is relevant for.
Classify Condition Types
Specify which condition types you want to use
for condition-based excise determination.
Define Tax Accounts
Check which G/L accounts the various taxes will
be posted to. Define G/L accounts for the account keys used in the tax procedure
6 MM
Materialwirtschaft
16.1 Country Version India in Standard R/3 System
Verwendung
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), Country Version India is no longer
delivered as an add-on but as part of the standard R/3 System.
Integration of functions in the SAP Easy Access menu
The functions for withholding tax have been integrated into the SAP Easy Access menu, under
Accounting -> Financial Accounting -> Accounts Payable -> Withholding Tax ->
India and Accounting -> Financial Accounting -> Accounts Receivable -> Withholding
Tax -> India.
You can access all other functions using the area menu J1ILN, which you can call from the
SAP Easy Access screen using the transaction code J1ILN.
Country Version India Implementation Guide
The Country Version India Implementation Guide (IMG) has been integrated into the standard
Reference IMG (see Changes to Structures for Country Version India).
Release Notes
You can access release notes from previous add-on releases using the links below.
SAP Library Documentation
The SAP Library documentation for Country Version India is also delivered on the standard
SAP Library documentation CD (see below).
New and Changed Functions
For information about new and changed functions for Country Version India, see the other
release notes for this release.
Auswirkungen auf den Datenbestand
You do not need to change any data.
Auswirkungen auf das Customizing
IMG activity
What to do
Activate Country Version India for Specific Fiscal Years
Delete the entry ZIND and
create a new entry for IND.
Siehe auch
SAP Library -> Financials or Logistics -> Country Versions -> Asia-Pacific -> India.
Release Notes from Country Version India Add-On (FI)
Release Notes from Country Version India Add-On (SD)
SAP AG
1
SAP-System
Page 9
Release Notes from Country Version India Add-On (MM)
16.2 Condition-Based Tax Calculation (New)
Verwendung
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), a new method for calculating taxes
in Brazil is available, which makes use of the standard condition technique. Tax rates, tax laws,
and special indicators that influence whether tax line items are included in the nota fiscal are all
stored in the system as condition records. An additional tax calculation procedure, TAXBRC, is
delivered for this new method, in addition to the existing one for Brazil, TAXBRJ.
Auswirkungen auf den Datenbestand
You can continue to calculate taxes using the former method: when the system processes the tax
procedure assigned to the country (TAXBRJ), it calculates the taxes externally by calling
function module J_1BCALCULATE_TAXES. We do, however, recommend that you assign the
new procedure TAXBRC and use the condition-based tax calculation functions, as it enables you
to flexibly adapt the tax calculation logic to cover new legal requirements or special customer
needs.
You will need to migrate your existing tax rate table entries to condition records, which you
can do directly from the Tax Manager's Workplace described below. You can check all tables
and subsequently convert the entries, whereby the system generates condition records. After the
initial migration, each time you create or change a tax rate table entry, the system automatically
generates a condition record as needed.
Auswirkungen auf das Customizing
If you want to employ the new condition-based tax calculation, you need to activate it and
carry out all related Customizing activities, under Financial Accounting -> Financial
Accounting Global Settings -> Tax on Sales/Purchases -> Basic Settings -> Brazil
-> Condition-Based Tax Calculation, all of which are new:
o
Activate Condition-Based Tax Calculation
o
Map MM Tax Values to Nota Fiscal Fields
o
Map SD Tax Values to Nota Fiscal Fields
o
Map MM Tax Laws to Nota Fiscal Fields
o
Define Internal Codes for Tax Conditions
o
Assign Internal Codes for Tax Conditions to Condtion Types
o
Assign Tax Rate Tables to Condition Tables
In addition, you need to assign the new tax calculation procedure TAXBRC to the country in
Customizing, under Financial Accounting -> Financial Accounting Global Settings ->
Tax on Sales/Purchases -> Basic Settings -> Assign Country to Calculation Procedure.
A new Customizing tool called the Tax Manager's Workplace is available that enables you to
SAP AG
2
SAP-System
Page 10
make all tax-related settings for Brazil. You access it under the same path as above through
Tax on Sales/Purchases, then Calculation -> Settings for Tax Calculation in Brazil ->
Access Tax Manager's Workplace, or alternatively by entering transaction J1BTAX. You can
use the Tax Manager's Workplace regardless if you use condition-based tax calculation; it
simply brings all tax activities to a single transaction (only the Migration, Nota-Fiscal Mapping,
and Condition Mapping options under the Condition Setup pulldown menu are relevant only for
condition-based tax calculation).
16.3 Changes to Structures for Country Version India
Verwendung
As of SAP R/3 4.7, Country Version India is no longer delivered as an add-on, but forms part
of the standard system.
SAP has discontinued the Country Version India Implementation Guide (IMG) and has added its
activities have been added to the standard Reference IMG as follows:
Activities relating to withholding tax are now located in Customizing for Financial
Accounting (FI), under Financial Accounting Global Settings -> Withholding Tax.
Activities relating to excise duty and excise invoices are in Customizing for Logistics -
General, under Tax on Goods Movements -> India.
As far as the activities under Preparatory Activities are concerned, two of them (Activate
Country Version India for Accounting Interface and Activate Processes) are no longer
relevant and have been removed from the IMG entirely. The activity Execute Country
Installation Program is already included in the standard IMG under the name Localize Sample
Organizational Units. And the other two activities (Activate Country Version India for Specific
Fiscal Years and Activate Business Transaction Events) have been added to the standard IMG.
For information about other changes to the IMG relating to changes in the functions in Country
Version India, see the other release notes.
16.4 Release Notes from Country Version India Add-On (MM)
Verwendung
The Release Notes from Releases 3.0A and 4.0A of Country Version India for Materials
Managment (MM) are listed below. For more Release Notes, see the alias globalization in
SAPNet, and choose Media Center -> Country-Specific Documentation -> Country Version
India - Release Notes.
Release 3.0A
o
CENVAT Credit on Capital Goods After Budget 2000 (Changed)
o
Multiple Goods Receipts for Single Excise Invoices
SAP AG
3
SAP-System
Page 11
o
Enhancements to CVD Solution
o
Pricing Date Control in Excise
o
Order Price Unit in Excise
o
Alternate Assets MODVAT Capitalization
o
Enhancements for 57 F4
o
User Exits for Customer Validations
Release 4.0A
o
Procurement Transactions for Excise Invoices
o
New Transactions Based on User Roles for Incominng Excise Invoices
o
Capture Excise Invoices with Reference to Multiple POs for the Same Vendor
o
Capture Excise Invoice and Post CENVAT in a Single Step
o
Open Schedule Quantity Defaulted in Excise Capture for Scheduling Agreement
o
Accounting Document Simulation for CENVAT Postings
o
Rejection Codes for Excise Invoices
o
Single-Screen Transaction for All Excise-Related Entries
o
Stock Transfer Orders Through MM Route
o
Excise Invoices for Multiple Import Purchases
o
Customs Invoices Can Be Captured Using Logistics Invoice Verification and Conventional
Invoice Verification
o
Material Type at Line Item Level
o
Excise Invoice Capture Without PO
o
Excise Invoice Without PO - Capture and Post in a Single Step
o
Recalculation of Duty and Excise Defaults Restore Feature Available
o
Split of Nondeductible Taxes During Excise Invoice Capture
o
Error or Warning Messages Displayed at the Time of Saving
o
Reversal of Excise Duty
o
MIGO Solution Available as a Note 0408158 (Featuring All Functionalities as in MB01)
o
Excise Invoice Defaults in Excise Popup at Goods Receipt
o
Split Accounting Lines for CENVAT Posting
o
Authorization for Incoming Excise Invoices Extended
o
Authorization Available for Part I Entry at GR
o
Authorization Available for Register Update Transaction
o
User Exit Available for Incoming Excise Invoice Transaction for Defaulting Values
SAP AG
4
SAP-System
Page 12
o
User Exit Available for Incoming Excise Invoice Transaction Before Database Update
o
User Exit Available for Register Update for Validations on Fetched Records Based on
Selection Criteria
o
User Exit Available for Register Update of RGSUM Register
o
User Exit Available for Excise Invoice Create for Other Movements to Default the Excise
Details
o
Register Update Separately Handled for Receipts and Issues Based on Classification Code
o
Ship-From Vendor Can Be Defaulted and Captured in Incoming Excise Invoices for Other
Movements
o
Removal Time Can Be Captured in Excise Invoices for Other Movements
o
Field Selection of Incoming Excise Invoices
o
Transaction Code Customizing for Incoming Excise Invoices
o
Excise Group Setting for Part I Indicator for Blocked Stock, Stock Transfer Order, and
Consumption Stock
o
Multiple Goods Receipts and Multiple/Single Credit Settings Available at Excise Group
Level
o
Rejection Code Master Setting for Posting on Hold Is Available
o
Stock Transport Orders

MAP fiscal year as per Vikram Samvat

Hi
I have a requirement for defining the fiscal year according to Hindi Calender i.e. Vikram Samvat wherein first month starts from mid of july sometimes 16th, sometimes 17th etc.
again here no. of days in a month can go up from 29 to 32 days not fixed for all years.
Can anybody tell how to map it?
Regards
Ajay

I am not sure about this
but I think only SAP can help you on this i have never seen or read any such requirement on SDN or anywhere else before today

Here maps: Unable to download portugal for offline...

I am unable to download portugal for offline use. I tried a few other maps and could download them. It gets stuck on "preparing download 0%".
Nokia Lumia 920. Version of here maps is 3.5.487.8, mapdata 8.30.53.110.
It's all very dissapointing since I'm going to Portugal in about 36 hours.
I have been trying to download this map the whole day.

I will make it a little easier for whatever support does exist out there..
I can download other maps fine (tried sweden and belgium).
However I cannot download portugal map, or update any of the downloaded maps I already have.
I tried restarting the phone
I reinstalled the Here maps app
I am 100% sure I have internet connection via WiFi(100mbit fiber). Obviously since I could download other maps.
However just a few minutes ago I was able to update maps and download my portugal maps. I want to mention that I downloaded two other maps while trying and portugal map never worked until just a few minutes ago, neither did updating current maps.

PIS e COFINS retidos nao trasferidos na Nota Fiscal

Boa tarde gente!
Depois de ter sempre ajuda de voces no nosso projeto da NFE, espero ter a mesma sorte agora com o SPED PIS/COFINS.
Tamos com o problema que os impostos retidos calculados na fatura SD nao sao trasferidos na Nota Fiscal.
As condiçoes em SD ficam assim (resumidos):
BW12     WHT Rate PIS     0,650      %                    0,09
BW22     WHT Rate COFINS     3,000      %                    0,42
BW32     WHT Rate CSLL     1,000      %                    0,14
BW42     WHT Rate IR                          1,200      %                    0,17
Segui as instruçoes do "Customizing Guide: New Taxes 2004 (ISS, PIS, COFINS, MP-135 Withholding Taxes)" da nota 727475.
E acho que temos certo a parte do mapeamento de SD com a NF (Tax Manager). Ejemplo:
Usage           A
Application     V
Pric. procedure RVABRA
Tax type        ICOW
Tax Rate Cond.      BW22           Field Mapping     1
Pauta Rate Cond.                        Field Mapping     0
Tax Amount Cond.    BW22        Field Mapping     0
Total Base Cond.    BXWT          Field Mapping     0
Tax Base Cond.      BXWT          Field Mapping     0
Ex. Base Cond.                           Field Mapping     0
Other Base Cond.                       Field Mapping     0
WHT Collection Code BW21
Base Red.                                  Field Mapping     0
St. Base Red                              Field Mapping     0
Mas na nota fiscal so tenho os valores do ICMS e IPI:
ICM3     ICMS from SD     ICMS
IPI3     IPI from SD     IPI
Espero que foi capaz explicar o nosso problema e que voces tem alguma idea o sugerencia!
Como sempre: muito obrigado ja pela ajuda!
Abraços
Nino

Boa tarde gente!
Achei problema e soluçao! O nosso cliente ta com o SAP 4.7 e SP35, mas eles nao tenhiam todas as configuraçoes manuais relacionadas com SPED PIS/COFINS.
Nesse caso teve que configurar as indicaçoes da nota 916003.
Bom trabalho a todos!
Abraços
Nino

How to add FISCAL YEAR, Period and Day to cube.

hi,
I am using SD EXTRACTORS (2LIS_11_VAITM, 2LIS_11_VAKON, 2LIS_12_VCITM and 2LIS_13_VDITM) and directly updating each corresponding ODS and cube.
All the extractors only have FISCAL VARIANT has the time characteristic. So, all my ODS contains only one time char - fiscal variant and other dates (liek document created date etc. (not a time char)).
Now, I want to use fiscal period, fiscal year and fiscal day in my cube. I have added these time char in my cube.
My question:
1. how to get FISCAL YEAR, FISCAL PERIOD and FISCAL DAY get updated. Do I need to map to document created date in update rules or Do I need to use some functional module.
Pls note I am bringing only FISCAL VARIANT from R/3 into ODS and then to CUBE.
PLS REPLY.

thanks sundar..i got your point..but I have one question
All the cubes (sales, sales condition and billing) have the sales order number (VBUK-VBELN) and item number (POSNR-VBUK). But info objects used for these fields in sales cube and sales condition cube are same but for billing it is not same.
Can I combine all cubes (sales order, sales condition, billing) in muliti provider.
1. Sales order cube (from VAITM)
           Sales order number (VBUK-VBELN) -- (0DOC_NUMBER)
           Sales Item (VBUK-POSNR)              -- (0S_ORD_ITEM)
Date : Document created date (VBAK-AUDAT) -- 0DOC_DATE
2. Sales Condition cube (from VAKON)
           Sales order number (VBUK-VBELN) -- (0DOC_NUMBER)
           Sales Item (VBUK-POSNR)              -- (0S_ORD_ITEM)
Date: Document created date (VBAK-AUDAT) -- 0DOC_DATE
Key field: Netprice (VBAP-NETWR) -- 0NET_VALUE
3. Delivery Cube (from VCITM)
         Sales order number (VBUK-VBELN)   -- (0DELIV_NUMB)
         Item   (VBUK-POSNR)                         -- (0DELIV_ITEM)
Date: Delivery Date :LIKP-WADAT_IST      -- 0ACT_GI_DTE
4. Billing Cube (from VDITM)
          Sales order number (VBUK-VBELN) -- (0BILL_NUM)
          Sales Item (VBUK-POSNR)              -- (0BILL_ITEM)
Date: Billing Date: (VBRK-FKDAT)             -- (0BILL_DATE)
Key field: Net price (VBRP-NETWR)       -- 0NETVAL_INV
I want to combine above cubes. If I combine, Will I get correct data??????
Points will be assigned to every useful answer

C3 - Google Maps don't work whith gprs

Hi,
I am from Portugal and I am a vodafone client.
I want to use google maps whith gprs connection but, as others apps that I download from ovi store, anyone works. It say internet connection fail alltimes...
I think is a configuration issue, but i try some changings in config, and nothing work.
Apps like communites and mail, that came whith the cell, work fine.
Can anyone help?
Tanks!

andrejs,
I just tried the tutorial (works fine) and the tutorial with ADF security (works fine). It seems to be something more specific to your application than anything else.
John

Calendar day and Calendar Year/Week mapping

Dear SDN,
I am unable to view Calendar Year/Week and Calendar Day ...Data..
I have observed that they have not mapped in the Update rules of 0SD_C03 InfoCube...
I have checked all the InfoSources (2LIS_11_VAHDR, 2LIS_11_VAITM, 2LIS_11_V_ITM, 2LIS_12_VCHDR, 2LIS_12_VCITM, 2LIS_13_VDHDR, 2LIS_13_VDITM)...
There in all the Update Rules...
Update Rules -- Details -- Time Ref.---
Time Characteristic of Fiscal Year Variant is mapped with Source fields of Fiscal Year variant
similarly,
Calendar Year/Month is mapped with Update Date Statistics
But Calendar Year/Week and Calendar Day are Blanck...
I am thinking they also should be mapped..
Please suggest me how to resolve this...
Help will be greatly appreciated with points..
Thanks in advance..
This is very urgent...

Thanks...
But i have already assigned my self...
0calyear/week to Update date statistics...
and
0calendarday to Update date statistics..
I have assigned points to you...
Thanks for your informatioon

Fiscal Period in 0PA_C01

The cube 0PA_C01 works on the basis of calmonth and it is easy to map it to fiscal period if each fiscal period corresponds to a whole calendar month.
But we are facing a peculiar situation where the Client's fiscal periods are irregular and do not correspond to exact calendar months.For example Fiscal Period 01.2009 corresponds to the period 02.04.2009 to 29.04.2009 and not to Calendar month April'09.
In such a case it is becoming a challenge to extract the headcount on the basis of fiscal period from the cube 0PA_C01.
Could any one offer a clue as to how this could possibly be achieved?

Hello Rajeev,
you can always use FM DATE_TO_PERIOD_CONVERT during extraction in ZXRSAU01 or in transfer/update rules on BW. Remember to transfer Global Settings from source system to BW when using second method. Don't forget about transfer data to 0FISCVARNT as well.
Thanks = points.
Best Regards,
Maciej Janik

Using fiscal period and Fiscal quarter reporting seemlessly in a BI Query

Hi,
We have a very specific issue. Reporting the Fiscal Period( in our
case we have 53 fiscal periods) and Fiscal Quarter( we have 4 quarters)
in the same query seamlessly as we would have done using Calander Month
and Calander quarter in other reports that uses SAP delivered standard
time dimensions.
However unlike the Calander time dimension (SAP provided all
possible...0CALDAY, 0CALWEEK, 0CALMONTH, 0CALQUARTER, 0CALYEAR) where you have all of these inside your info provider, you can get
aggregation on week, month, quarter etc in your query seamlessly, The Fiscal Year/Period offers a problem in doing report seamlessly.
When we delve into Fiscal realm, SAP only provided with 0FISCVARNT,
0FISCPER, 0FISCYEAR and a special period 0FISCPER3. It doesn't provide
anything like 0FISCQUARTER etc and rightly so, because you can have
only one 0FISCVARNT in the Time dimension and can have related periods
(0FISCPER) only for a Row of data in your infocube. For example if you need to model as per the Fiscalweek, you can create a custom Fiscal year variant (Say z1) and can configure to have only 53 periods (Mapped to 0FISCPER) representing
53 Fiscal WEEK. Similarly for mapping Fiscal Quarter you can create
another fiscal year variant (Say Z2) and have only 4 periods (mapped to
0FISCPER also in this case) to represent the 4 Fiscal Quarter. However
the issue is that for one record you can only map either of those and
not both since you can only have one Fiscal year variant in one row of
data in the info provider.
For example
If I have two rows OF DATA coming from different sources (One FOR
Fiscal Week and another for Fiscal Quarter) I can have the following in
my info provider.
1> Example data in Fiscal
Char1 Char2 0CALDAY 0FISCVARNT 0FISCPER Quantity
X ...... y .....10/22/07 ....Z1 .... 432007 .......10
X ....... Y .....10/22/07 ....Z2 .... Q32007 .......20
The issue is how do I report the Quantity in a query in Quarter Q3 as
(10 + 20 = 30) since both the rows corresponds to FISCAL Q32007?
(Please note that Fiscal week 432007(For VARIANT Z1 ) actually is
Fiscal Quarter Q32007( For Fiscal Variant Z2) as per our
configuration of Fiscal Year Variant configuration Z1 and Z2)
The same is very simple when I have infoprovider with CALENDAR Time
dimensions , for example if we dont have any fiscal reporting
requirement and just report on calendar time dimension the record in
the info provider would look like the following ( example)
2> Example Data in CALENDAR DIMENSION
Char1 Char2 0CALDAY 0CALWEEK 0CALQUARTER Quantity
X ........ y .......10/22/07 .......432007 .......Q32007 .......10
X ........Y .......10/22/07 ....... 442007 .......Q32007 .......20
Here we can use both 0CALQUARTER and get the data aggregated on the
quarter level in addition to the 0CALWEEK.
To solve this issue, One option that we are thinking of Using 0CALQUARTER to represent the
Fiscal Quarter and use Update rule to populate this one. For example
THE example 1 can be as follows.
1A> Example of using 0CALQUARTER along with 0FISCVARNT and 0FISCPER
Char1 Char2 0CALDAY 0FISCVARNT 0FISCPER 0CALQUARTERE Quantity
X .......y .......10/22/07 ..............Z1 .......432007 .......Q32007 ..............10
X .......Y .......10/22/07 ..............Z2 .......Q32007 .......Q32007 ..............20
In this case we would populate the 0CALQUARTER by the actual Fiscal
Quarter and then can use both as per example 2 above. But this is not a
smooth option since we have various other info providers to join and
report based on solely Fiscal Quarter etc
I am certain that this issue have already been solved by somebody as this bound to happen in any finance application.
Would appreciate if we can get some light on this regarding the data modelling, reporting etc.
Thanks
Arun G.

You have yourself suggested a solution, which is fine,
Other option is to have a new characteristic Fiscal Qtr in all the infoproviders ans update the same using a routine in the updaterule depending on the fiscal year variant.
for eg. for transaction with variant Z1 in one case you can say if fiscal week 01 between 01 to 13 the Fiscal Qtr should be update with1 and if it is between 14 to 26 then update fiscal qtr with 2 and so on.
For other Variants Z2 you write a different login in the routine ans so on.
so for all the data irrespective of the variant you will have the qtr as either 1 or 2 or 3 or 4 and you can report on this fiscal qtr.
assign points if it helps.
regards
Venkata Devaraj

Strange Data Mapping Errors after SEM 6 Upgrade. Please assist.

Hi All, I encountered these sudden Mapping errors after I tried to do Testing in Post Upgrade Sand Box. Here I am trying to to perform Collected Reported Financial Data under Data Collection Method for a particular Company Code 3040. Kindly help me with some quick responses as this is kind of high priority. The errors and the Diagnosis Notes I am unable to follow as I do not where I shall write those Mapping Rules they are referring to. I do not even know if that need to apply any SAP Notes as such. Once again Highly appreciate your quick response and Many Thanks in Advance.
Regards, BIP
Input conversion for field Period Value LC has invalid format Message no. UCT8210 Diagnosis The mapping rule for target field Period Value LC contains a move with a selected Input Conversion indicator. Therefore, the system performs an input conversion prior to creating the target data. However, an error in the input conversion occurred while moving the source key figure to the target key figure Period Value LC. This means that the format used for the input conversion is incompatible with the target data. System Response The system will not perform the move. Procedure Examine the mapping rule for field Period Value LC. Either select the Conversion Exit indicator or deselect the Input Conversion indicator. Execute the method again. -
3040 is incompatible with input format for field /1FB/COMPANY Message no. UCT8258 Diagnosis During execution, the method derives the source selection for source field /1FB/COMPANY from the mapping rule for the target field. 3040 is one of the values that were derived for the source selection. The system requires that this value is in the correct SAP-internal format because the Conversion Exit indicator has been selected in the move operator for field /1FB/COMPANY. However, the value 3040 is incompatible with the SAP-internal format. System Response The system attempts to interpret value 3040 as an external format and convert it to the internal format. If this fails, the system is unable to restrict the source selection using source field /1FB/COMPANY. In this case, the system may read more source data than was originally intended, which can affect performance. Procedure In the log, choose the Source button to display the source selections that are used to read the source data. When this appears, examine values selected for field /1FB/COMPANY. If the correct values were selected, you can ignore this message. To prevent this message from being issued, you can select the indicator in the mapping rule used by source field /1FB/COMPANY. If incorrect values were selected, make sure that the mapping rule used by source field /1FB/COMPANY has been defined correctly. If the mapping rule is correct and value (3040) derived for the source selection does not affect the overall result, you can ignore this message. If the source selection does not contain the value 3040 for field /1FB/COMPANY and, because of this, source data that is supposed to be read is not being read, make sure that the mapping rule has been defined correctly. If the source selection does not contain any value for field /1FB/COMPANY, make an estimation as to how much excess source data is being read and whether this might affect system performance. If you do not expect any performance problems, you can ignore this message. In any event, you have the following alternatives if the mapping rule is defined correctly, but the source selection on field /1FB/COMPANY is unsatisfactory: You can define a source selection for field /1FB/COMPANY in the Customizing settings for the method on the Selection tab page. Then the method uses this source selection instead of the source selection derived from inverse interpretation of the mapping rule. You can implement the Business Add-In (BAdI) UC_DATATRANSFER and use the method INVERT to determine the source selection on field /1FB/COMPANY. Then the method uses the result of the INVERT method for the source selection instead of the source selection derived from inverse interpretation of the mapping rule. -
Cannot derive the source selection from target field Version Message no. UCT8252 Diagnosis Field Version has one of the following roles: Consolidation unit Group currency key Fiscal year Posting period Version To delimit the volume of the source data to be read, the system usually derives the source selection from the target selection of such a field. However, the system cannot derive a source selection from field Version. System Response It is possible that a greater volume of source data is being read than is necessary. This can lead to performance issues. Procedure Check whether a mapping rule is defined for field Version. If a mapping rule is defined, you can disregard this warning message. However, if you discover after method execution that the system did not process a large amount of data, and that system performance was not satisfactory, you may want to examine the source selection by choosing the Source button in the log. If the reason for the disregarded data is that too much source data was read because of the unrestricted selection on the source field (which is linked with target field Versionthrough mapping), choose one of the alternatives below: Change the mapping rule for field Version so that the system can derive a delimiting source selection. Implement the Business Add-In (BAdI) UC_DATATRANSFER with the method INVERT to delimit the selection for the source field that is linked via mapping to the target field Version. -
Cannot derive the source selection from target field Group Currency Message no. UCT8252 Diagnosis Field Group Currency has one of the following roles: Consolidation unit Group currency key Fiscal year Posting period Version To delimit the volume of the source data to be read, the system usually derives the source selection from the target selection of such a field. However, the system cannot derive a source selection from field Group Currency. System Response It is possible that a greater volume of source data is being read than is necessary. This can lead to performance issues. Procedure Check whether a mapping rule is defined for field Group Currency. If a mapping rule is defined, you can disregard this warning message. However, if you discover after method execution that the system did not process a large amount of data, and that system performance was not satisfactory, you may want to examine the source selection by choosing the Source button in the log. If the reason for the disregarded data is that too much source data was read because of the unrestricted selection on the source field (which is linked with target field Group Currency through mapping), choose one of the alternatives below: Change the mapping rule for field Group Currency so that the system can derive a delimiting source selection. Implement the Business Add-In (BAdI) UC_DATATRANSFER with the method INVERT to delimit the selection for the source field that is linked via mapping to the target field Group Currency
1 is incompatible with input format for field FISCPERIOD Message no. UCT8258 Diagnosis During execution, the method derives the source selection for source field FISCPERIOD from the mapping rule for the target field. 1 is one of the values that were derived for the source selection. The system requires that this value is in the correct SAP-internal format because the Conversion Exit indicator has been selected in the move operator for field FISCPERIOD. However, the value 1 is incompatible with the SAP-internal format. System Response The system attempts to interpret value 1 as an external format and convert it to the internal format. If this fails, the system is unable to restrict the source selection using source field FISCPERIOD. In this case, the system may read more source data than was originally intended, which can affect performance. Procedure In the log, choose the Source button to display the source selections that are used to read the source data. When this appears, examine values selected for field FISCPERIOD. If the correct values were selected, you can ignore this message. To prevent this message from being issued, you can select the indicator in the mapping rule used by source field FISCPERIOD. If incorrect values were selected, make sure that the mapping rule used by source field FISCPERIOD has been defined correctly. If the mapping rule is correct and value (1) derived for the source selection does not affect the overall result, you can ignore this message. If the source selection does not contain the value 1 for field FISCPERIOD and, because of this, source data that is supposed to be read is not being read, make sure that the mapping rule has been defined correctly. If the source selection does not contain any value for field FISCPERIOD, make an estimation as to how much excess source data is being read and whether this might affect system performance. If you do not expect any performance problems, you can ignore this message. In any event, you have the following alternatives if the mapping rule is defined correctly, but the source selection on field FISCPERIOD is unsatisfactory: You can define a source selection for field FISCPERIOD in the Customizing settings for the method on the Selection tab page. Then the method uses this source selection instead of the source selection derived from inverse interpretation of the mapping rule. You can implement the Business Add-In (BAdI) UC_DATATRANSFER and use the method INVERT to determine the source selection on field FISCPERIOD. Then the method uses the result of the INVERT method for the source selection instead of the source selection derived from inverse interpretation of the mapping rule
Input must be in the format ___,___,__~ Message no. 00088 Diagnosis Your entry does not match the specified input format. System Response The entry in this field was rejected. Procedure The entry must comply with the edit format. The following edit format characters have a special meaning: "_" (underscore) There should be an input character at this point; this should be a number for numeric fields. "." (decimal point) (applies to numeric fields) The decimal point occurs here (setting in the user master record). "," (thousands separator) (applies to numeric fields) This separator occurs (optionally) for more than three figures. Depending on the setting in the user master record, it can be a period or a comma. "V" (applies to numeric fields) The operational sign appears here. If used, it must by at the right margin of the field. The sign is either "-" or " "(space). "~" (tilde) (applies to numeric fields) As of and including this character, leading zeros must also be entered. Otherwise, this character has the same meaning as an underscore. Leading zeros need not be entered on the left of the tilde. They are not output at this position. All other characters have their normal meanings and must be entered in the same position as in the edit format.

Hi Dan,
Could you Kiindly advise me where we need to write the Mapping Rules in Consolidation Monitor? All he time the errors refering to Mapping Rules. The only Tab I seen "Mapping" is in Data Basis But as per my Understanding Iwe do not have much to do there as it is system generated Mapping Tab.
Where we actually go and select/deselct those Input Conversion Indicator/ Conversion exit Indicator.
Highly appreciate your advise.
Thanks and Regards,
BIP

HT5429 I am not able to get any directions on my maps i am using iphone 4s and updated to ios 6.1.3 and whenever i try to find a route it always says directions could not be found can anyone help in fixing it

I am not able to get any directions on my maps i am using iphone 4s and updated to ios 6.1.3 and whenever i try to find a route it always says directions could not be found can anyone help in fixing it

Maps: Turn-by-Turn Navigation
Argentina Australia Austria Belgium Brunei Bulgaria Canada Croatia Czech Republic Denmark Egypt Estonia Finland France Germany Greece Hong Kong Hungary Ireland Israel Italy Japan Latvia Liechtenstein Lithuania Luxembourg Macau Malaysia Malta Mexico Morocco Netherlands New Zealand Norway Poland Portugal Romania Russia San Marino Singapore Slovakia Slovenia South Africa South Korea Spain Sweden Switzerland Taiwan Thailand Turkey UK Ukraine USA
Back to Top

Mapping of field with MinOccurs 0 in SAP XI 2.0 SP5

Hi,
Our Scenario is
File -> Adapter -> XI -> Idoc Adapter -> SAP
We are trying to push IDoc and the mapping tool is giving an error. I am providing the error that I am getting.
The snippet of the XSD for the IDoc is given below:
   <xsd:element name="E1FIKPF" minOccurs="1" maxOccurs="1" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                        <xsd:annotation>
                           <xsd:documentation>FI Document Header (BKPF)</xsd:documentation>
                        </xsd:annotation>
                        <xsd:complexType>
                           <xsd:sequence>
                              <xsd:element name="BUKRS" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                                 <xsd:annotation>
                                    <xsd:documentation>Name of global company code</xsd:documentation>
                                 </xsd:annotation>
                                 <xsd:simpleType>
                                    <xsd:restriction base="xsd:string">
                                       <xsd:maxLength value="6" />
                                    </xsd:restriction>
                                 </xsd:simpleType>
                              </xsd:element>
                              <xsd:element name="BELNR" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                                 <xsd:annotation>
                                    <xsd:documentation>Accounting Document Number</xsd:documentation>
                                 </xsd:annotation>
                                 <xsd:simpleType>
                                    <xsd:restriction base="xsd:string">
                                       <xsd:maxLength value="10" />
                                    </xsd:restriction>
                                 </xsd:simpleType>
                              </xsd:element>
                              <xsd:element name="GJAHR" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                                 <xsd:annotation>
                                    <xsd:documentation>Fiscal Year</xsd:documentation>
                                 </xsd:annotation>
                                 <xsd:simpleType>
                                    <xsd:restriction base="xsd:string">
                                       <xsd:pattern value="\d+" />
                                       <xsd:maxLength value="4" />
                                    </xsd:restriction>
                                 </xsd:simpleType>
                              </xsd:element>
                              <xsd:element name="BLART" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                                 <xsd:annotation>
                                    <xsd:documentation>Document type</xsd:documentation>
                                 </xsd:annotation>
                                 <xsd:simpleType>
                                    <xsd:restriction base="xsd:string">
                                       <xsd:maxLength value="2" />
                                    </xsd:restriction>
                                 </xsd:simpleType>
                              </xsd:element>
                              <xsd:element name="BLDAT" minOccurs="0" type="date" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                                 <xsd:annotation>
                                    <xsd:documentation>Document Date in Document</xsd:documentation>
                                 </xsd:annotation>
                              </xsd:element>
                              <xsd:element name="BUDAT" minOccurs="0" type="date" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                                 <xsd:annotation>
                                    <xsd:documentation>Posting Date in the Document</xsd:documentation>
                                 </xsd:annotation>
                              </xsd:element>
                              <xsd:element name="MONAT" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                                 <xsd:annotation>
                                    <xsd:documentation>Fiscal Period</xsd:documentation>
                                 </xsd:annotation>
                                 <xsd:simpleType>
                                    <xsd:restriction base="xsd:string">
                                       <xsd:pattern value="\d+" />
                                       <xsd:maxLength value="2" />
                                    </xsd:restriction>
                                 </xsd:simpleType>
                              </xsd:element>
In this snippet as can be seen the minOccurs for the BUKRS field is 0. But if I do not map the field its giving me following error.
/usr/java131/bin/javac -encoding UTF8   -classpath .:./system-lib/boot.jar:./system-lib/jaas.jar -extdirs ./additional-lib:./services/deploy/work/applications/ExchangeRepository -d /tmp/9_53_35_27_7_2004 /tmp/9_53_35_27_7_2004/com/sap/xi/tf/_MsgMapGcentre2Fidcc2_.java
/tmp/9_53_35_27_7_2004/com/sap/xi/tf/_MsgMapGcentre2Fidcc2_.java:303: ';' expected
a117.gotoNextContext();tmpValAtr = a117.getValue();if (!tmpValAtr.equals(SUPPRESS)) handler.addAttribute("SEGMENT", tmpValAtr);a117.gotoNextValue();if (!__deflt)a115.gotoNextValue();No mapping for value/FIDCCP02/IDOC/E1FIKPF/BUKRS
                 ^
/tmp/9_53_35_27_7_2004/com/sap/xi/tf/_MsgMapGcentre2Fidcc2_.java:303: cannot resolve symbol
symbol : class No
location: class com.sap.xi.tf._MsgMapGcentre2Fidcc2_
a117.gotoNextContext();tmpValAtr = a117.getValue();if (!tmpValAtr.equals(SUPPRESS)) handler.addAttribute("SEGMENT", tmpValAtr);a117.gotoNextValue();if (!__deflt)a115.gotoNextValue();No mapping for value/FIDCCP02/IDOC/E1FIKPF/BUKRS
^
2 errors
Compilation error
Any one having any guesses on why this error is coming. I know this error would vanish if we map the field by an Empty Constant. But then it would start giving error for the next field until all the non mandatory fields are mapped.
If however I go ahead and map all the fields then the output structure generates all the segments the maxOccurs times. i.e. if a segment is occuring 999 times then that segment is repeated that many time in the output whereas I never needed that segment in the output.
Can any one suggest as to why this is happening. Am I doing some thing wrong or this is a problem with Mapping Editor in XI 2.0 SP5.
Ashish

Hello Ashish,
this is a bug in the mapping tool. You have to apply the note 730081. It says:
Symptom
After you import XI20 Support Package 04 or Support Package 05, you can
no longer change and regenerate the message mapping (graphic mapping
tools).
The following error is displayed during activation or generation: No
Mapping for value.......
Other terms
Graphic mapping tools, SAPINTSER05, no mapping vor value
Reason and Prerequisites
This problem is caused by a translation error.
Solution
The translation error has been corrected.
As of patch level 1, the correction is provided in the SAPINTSER05_1.sca
archive of the INTEGRATION Services 2.0 software component and, as of
patch level 2 for Support Package 5, it is provided in the
SAPINTBUI05_2.sca archive of the INTEGRATION BUILDER 2.0 software
component. The archives are available on the SAP Service Marketplace at:
http://service.sap.com/patches
SAP EXCHANGEINFRASTRUCTURE/SAP EXCHANGEINFRASTRUCTURE 2.0
Binary Patches/INTEGRATION SERVICES 2.0/OSINDEP and
..... /INTEGRATION BUILDER 2.0/OSINDEP
Import the archives using SDM.
The mapping must be recompiled after deployment.
Regards Franz

Data conversion for New GL - Going live during fiscal year

Hi Experts,
My client is going live on Oct 1 (fiscal year in Jan -Dec). So for data conversion we need to load P&L and BalanceSheet as of Sept 30, 2009. I need your help to resolve few open issues. (we have activated Doc Splitting with Zero Balance and Segment )
1) When we load P&L balances - how can I assign Profit Centers to all these P&L iitems .
2) What is the procedure (best practices) to assign Profit Centers to all the Balance Sheet items since we are going live during Fiscal Year
3) When we process open items (AR, AP) in month of October how the Profit Center assignment will work?
(My client will be using Profit /Cost center terminology first time, so we need to map all the B&S and PnL items to Profit centers)
4) What is the best way to map all the Balance Sheet GL accounts to Profit Centers.
Sorry for asking too many questions. Any help would me very much appreciated.
Thanks,
Sam

1) When we load P&L balances - how can I assign Profit Centers to all these P&L iitems .
Each P&L account balance has to be upload with cost centre, then automatically PC will be triggered.
2) What is the procedure (best practices) to assign Profit Centers to all the Balance Sheet items since we are going live during Fiscal Year
Let client decide the profit centre for balance sheet items, since they knows which balance relates to which pc
3) When we process open items (AR, AP) in month of October how the Profit Center assignment will work?
While uploading AR,AP balances, each line item to be uploaded with profit centre, automatically in october PC assignment will work.
(My client will be using Profit /Cost center terminology first time, so we need to map all the B&S and PnL items to Profit centers)
4) What is the best way to map all the Balance Sheet GL accounts to Profit Centers
Try to identify each balance sheet gl balance to each profit centre, this will help in future reports. otherwise put in common pc

GL Account Mapping After Upgradation

Hi Friends,
My requirement is as fallows anybody give some suggestion on this how to solve this issue:
When I have decided to shift the Fiscal year from mid calendar year to year end for AE, it was decided that we need to do a new implementation instead of an upgrade from 4.6C to ECC6. Thus the old 4.6C will be an archived system ending 31.12.2007 for reference and the new ECC6 system starts from 01.01.2008 for production transactions. The BI is the system which links both the 4.6C and ECC6 for management reports.
With the event of this new implementation of ECC6, AE has decided to restructure the GL account codes. The GL accounts will be assigned new numbers on the ECC6 systems. This is to allow for standardization and to cater for the ACM's current and future business needs.
If AE is to generate financial reports spanning 5 years, this would mean that, for example, 4 years from the 4.6C (old GL account numbers) and 1 year is from the ECC6 (new GL account numbers). It is not able to consolidate the 5 years figures as the GL accounts (although for the same purpose) have different numbers. That's when this mapping comes in, to map the old account to the new account.
siri

And your questions is what?
What problems have you got? or have you actually thought this through or put your managers request directly on this forum for free consulting advice?
If it were me I would look at taking in the mapping tables and either remodelling all the data in all the cubes (this is a HUGE project) by reading the new GL accounts
Now - depending on how they do take on data is how you will need to remodel the data
You WILL have duplicated data - as they will need to get opening balances into the new ECC6 system and these balances already exist in the old ERP system and thus in BW
So the first question is how are they going to actually going to restructure the ledger and how are they doing it? journals into period 0 etc?
IF you dont know this then whatever technical solutions are proposed are irrelevant - what does you FI BW consultant say - he/she will know the effect of the different scenarios

Portugal - Fiscal Maps immobilized

Similar Messages

Maybe you are looking for