Glossary entry (derived from question below)
English term or phrase:
Gaps(s)
Portuguese translation:
disparidade
Added to glossary by
Teresa Cristina Felix de Sousa
Sep 25, 2012 20:29
11 yrs ago
English term
Brazil
Teresa Cristina Felix de Sousa
Technical Translation Specialist
Native in: Portuguese
Works in: English to Portuguese
Gaps(s)
English to Portuguese
Marketing
SAP
Marketing de produtos
Gaps in ZALE and Sales BOM
1. What happens if the ZFIN is in R2 and the ZALE is needed in ECC?
2. How is CMIR used with the override?
3. OTC is best positioned to coordinate this solution
4. Need Gap Decision document
5. Gap, Stakeholders, comments, can we live with exception
1. What happens if the ZFIN is in R2 and the ZALE is needed in ECC?
2. How is CMIR used with the override?
3. OTC is best positioned to coordinate this solution
4. Need Gap Decision document
5. Gap, Stakeholders, comments, can we live with exception
Proposed translations
(Portuguese)
| 4 | disparidade |
cynthia07
|
| 3 | gaps(s) |
Clauwolf
|
Proposed translations
7 mins
Selected
disparidade
we're quite usde to using gap as an empty space between two things or words etc, but its meaning is a bit wider
4 KudoZ points awarded for this answer.
Comment: "Tks a lot, Cynthia7
Bjs
T."
4 mins
gaps(s)
:) Acho que fica gap mesmo
Gap Analysis: In simple terms: Gap means small cracks. In SAP world or in Information Technology world, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be."
Gap Analysis is undertaken as a means of bridging that space. Actual Gap Analysis is time consuming and it plays vital role in Business Blueprint[AS IS Process] stage.
A through Gap Analysis will identify the gaps between how the business operates and its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned,
1. GAP must be closed and customised software can be developed
2. GAP must be closed but software cannot be written therefore a workaround is required
3. GAP does not need to be closed.
A point worth mentioning here is that at time people confuse between user-exits and Gap Analysis. User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench, its not new functionality which we are trying to build in sap but its slight enhancement within the same code.
Gap analysis is start point of Realization and once business Blueprint is finished we have to find the realization of sap system for client requirment and there will be certain gaps when compared to system fit. Those gaps can be closed either by re-engineering of business process to fit with SAP or we have to use USER exits in case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system.
The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.
Gap Analysis: In simple terms: Gap means small cracks. In SAP world or in Information Technology world, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be."
Gap Analysis is undertaken as a means of bridging that space. Actual Gap Analysis is time consuming and it plays vital role in Business Blueprint[AS IS Process] stage.
A through Gap Analysis will identify the gaps between how the business operates and its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned,
1. GAP must be closed and customised software can be developed
2. GAP must be closed but software cannot be written therefore a workaround is required
3. GAP does not need to be closed.
A point worth mentioning here is that at time people confuse between user-exits and Gap Analysis. User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench, its not new functionality which we are trying to build in sap but its slight enhancement within the same code.
Gap analysis is start point of Realization and once business Blueprint is finished we have to find the realization of sap system for client requirment and there will be certain gaps when compared to system fit. Those gaps can be closed either by re-engineering of business process to fit with SAP or we have to use USER exits in case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system.
The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.
Something went wrong...