Requirement Translation

This entity represents the key information of a top level requirement, which includes the name, description, total estimates, etc. A top-level requirement is simlar to a requirements document containing other detailed requirements. For example, a top level requirement can be named Requirements for Flying Bike and within that top-level requirement, there could be multiple detailed requirement lines. Examples of requirement lines could be the need to be solar powered, the need to sync up with traffic controllers, etc. Each of those requirement lines would have priority, estimates etc. and the estimates would roll up to the top-level requirement.

QName: {http://xmlns.oracle.com/apps/scm/customerNeedsManagement/requirements/requirementService/}RequirementTranslation

Logical Business Objects

• SCM : Product Requirements and Ideation Management : Requirement

Relationships

The following table describes how this service data object is related to other service data objects or business object services.

Relationship Type	Object or Service
Contained by	Requirement Object
Handled by	Requirement Web Service

Attributes

The following table describes attributes in the service data object.

Name	Type	Description
Language	string	The language for the current record. Primary Key
Name	string	The name for the current record.
RequirementId	long	The unique identifier from the application for the requirement object. Primary Key
SourceLang	string	SourceLang is used to indicate the language in which the record is actually translated. For example, we may have a record for language = 'US' but containing attributes in French. In that case language attribute is set to 'US' and source_lang attribute is set to 'F'. If the record is translated on the current language, then Language attribute equals SourceLang attribute.