|
|
|
|
AppropriationRequest
No description is available
|
|
|
|
11-Dec-2005
|
|
|
|
|
Available Methods
- AddVariant : Create Appropriation Request Variant [ BAPI_APPREQUEST_ADDVARIANT ]
- AssignToExpenditureProgPos : Assign Appropriation Request to Investment Program Position(s) [ BAPI_APPREQUEST_ASSGNTOPROGPOS ]
- AssignVariantToVersion : Assign Appropriation Request to Plan Version(s) [ BAPI_APPREQUEST_ASSGNVRNTVERSN ]
- Change : Change Appropriation Request [ BAPI_APPREQUEST_CHANGE ]
- ChangeAssignmentToExpProgPos : Change Assignment of Approp. Request to Inv. Program Position [ BAPI_APPREQUEST_CHNGASSGNMNTIP ]
- ChangeVariant : Change Appropriation Request Variant [ BAPI_APPREQUEST_CHANGEVARIANT ]
- Create : Create Appropriation Request [ BAPI_APPREQUEST_CREATE ]
- Delete : Delete Appropriation Request [ BAPI_APPREQUEST_DELETE ]
- GetDetail : Display Appropriation Request [ BAPI_APPREQUEST_GETDETAIL ]
- GetStatus : Display Status of Appropriation Request [ BAPI_APPREQUEST_GETSTATUS ]
- RemoveVariant : Delete Appropriation Request Variant [ BAPI_APPREQUEST_REMOVEVARIANT ]
- ResetPlanValue : Reset Plan Values of Appropriation Request Variant [ BAPI_APPREQUEST_RESETPLANVALUE ]
- SetPlanValues : Change Plan Values of Appropriation Request Variant [ BAPI_APPREQUEST_SETPLANVALUES ]
- UnAssignExpenditureProgPos : Remove Assignment of Appropriation Request to Inv. Program Position [ BAPI_APPREQUEST_UNASSGNPROGPOS ]
- UnAssignVariantVersion : Remove Assignment of Appropriation Request to Plan Version [ BAPI_APPREQUEST_UASSGNVRNTVRSN ]
|
|
|
|
11-Dec-2005
|
|
|
|
|
AddVariant
The AppropriationRequest.AddVariant method is for creating anappropriation request variant for an existing appropriation request. NotesTo use this method, you need change authorization for the appropriation request.
This method works with buffering. This means that, in the same LUW,additional methods can change the data that was created and/or changedby this method, or other instances, without prior updating being necessary. The relationship between the import parameters Language and LanguageISO is as follows:
If the Language import parameter is filled, then the LanguageISO import parameter is ignored. If the Language import parameter is not filled, then the system usesthe value of the LanguageISO import parameter. If
neither of the two import parameters is filled, then the logon language is used as a default. Using this method, you can only create variants for already existing appropriation requests. Use the AppropriationRequest.Create method to create an appropriation request with exactly one variant.
For information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation alsodeals in detail with the use of the parameters and their limitations. Messages are returned in the parameter return. The parameter
documentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
AssignToExpenditureProgPos
The AppropriationRequest.AssignToExpenditureProgPos methodassigns an appropriation request to one or more investment programpositions. These investment program positions have to be end nodepositions. Assignment takes place by percentage. Budget categories are
supported, meaning that if budget categories are used in an investmentprogram, then it is possible to split the assignment to a program position according to budget categories. NotesTo use this method, you need change authorization for the appropriation
request. In addition, you need authorization for processing assignments to program positions. This method works with buffering. This means that, in the same LUW,additional methods can change the data that was created and/or changedby this method, or other instances, without prior updating being necessary.
For processing assignments to investment program positions, you can also use the following methods: AppropriationRequest.ChangeAssignmentToExpProgPos for changing assignments to investment program positions, and AppropriationRequest.UnAssignExpenditureProgPos for canceling assignments to investment program positions.
For information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation alsodeals in detail with the use of the parameters and their limitations. Messages are returned in the parameter return. The parameter
documentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library. For more information, refer to Investment Programs in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
AssignVariantToVersion
The AppropriationRequest.AssignVariantToVersion method assignsan appropriation request variant to one or more plan versions. NotesTo use this method you need change authorization for the appropriationrequest and for the variant. You also need authorization for version
assignment on the appropriation request, the variant, and the approval level of the plan version. This method works with buffering. This means that, in the same LUW,additional methods can change the data that was created and/or changedby this method, or other instances, without prior updating being necessary.
You can cancel the assignment of a variant to one or more plan versions using the AppropriationRequest.UnAssignVariantVersion method. For information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation also
deals in detail with the use of the parameters and their limitations. Messages are returned in the parameter return. The parameterdocumentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
Change
The AppropriationRequest.Change method changes the master data of an appropriation request. NotesTo use this method, you need change authorization for appropriation requests. This method works with buffering. This means that, in the same LUW,
additional methods can change the data that was created and/or changedby this method, or other instances, without prior updating being necessary. The relationship between the import parameters Language and LanguageISO is as follows:
If the Language import parameter is filled, then the LanguageISO import parameter is ignored. If the Language import parameter is not filled, then the system usesthe value of the LanguageISO import parameter. If
neither of the two import parameters is filled, then the logon language is used as a default. Using this method, it is not possible to change any of the following: Assignments to investment program positionsMaster data of variants
Plan values of variantsAssignments of variants to plan versionsFor these aktivities, use the following methods: AppropriationRequest.AssignToExpenditureProgPos, AppropriationRequest.ChangeAssignmentToExpProgPos,
AppropriationRequest.UnAssignExpenditureProgPos, AppropriationRequest.ChangeVariant, AppropriationRequest.SetPlanValues, AppropriationRequest.ResetPlanValue,
AppropriationRequest.AssignVariantToVersionAppropriationRequest.UnAssignVariantVersionFor information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation also
deals in detail with the use of the parameters and their limitations. Messages are returned in the parameter return. The parameterdocumentation shows the return codes and their meanings. Further Information
For more information, refer to Appropriation Requests in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
ChangeAssignmentToExpProgPos
The AppropriationRequest.ChangeAssignmentToExpProgPos methodchanges the assignment of an appropriation request to investment program positions. NOTE: All existing assignments of the appropriation request to investment programs are cancelled. Therefore, the AssignmentToPos
parameter has to contain a complete, 100% distribution of the assignment of the appropriation request to investment programposition(s). NotesTo use this method, you need change authorization for the appropriationrequest. You also need authorization for processing assignments to program positions.
This method works with buffering. This means that, in the same LUW,additional methods can change the data that was created and/or changedby this method, or other instances, without prior updating being necessary. Using this method, it is not possible to assign an appropriation
request, which does not have an assignment to an investment program position, to an investment program position, or to remove theassignment to an investment program positionen. The following methods can be used for those activities: AppropriationRequest.AssignToExpenditureProgPos
AppropriationRequest.UnAssignExpenditureProgPosFor information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation alsodeals in detail with the use of the parameters and their limitations.
Messages are returned in the parameter return. The parameterdocumentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library.
For more information, refer to Investment Programs in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
ChangeVariant
The AppropriationRequest.ChangeVariant method changes the master data of a variant of an appropriation request. NotesTo use this method, you need change authorization for the appropriation request and change authorization for the variant.
This method works with buffering. This means that, in the same LUW,additional methods can change the data that was created and/or changedby this method, or other instances, without prior updating being necessary. The relationship between the import parameters Language and LanguageISO is as follows:
If the Language import parameter is filled, then the LanguageISO import parameter is ignored. If the Language import parameter is not filled, then the system usesthe value of the LanguageISO import parameter. If
neither of the two import parameters is filled, then the logon language is used as a default. Using this method, it is not possible to change the plan values of thevariant or the assignment of the variant to plan versions. For these activities, use the methods below:
AppropriationRequest.SetPlanValuesAppropriationRequest.ResetPlanValueAppropriationRequest.AssignVariantToVersionAppropriationRequest.UnAssignVariantVersion
For information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation alsodeals in detail with the use of the parameters and their limitations. Messages are returned in the parameter return. The parameter
documentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
Create
The AppropriationRequest.Create method creates a new appropriation request with exactly one variant. NotesTo use this method, you need authorization for creating an appropriation request, for editing plan values, for assigning
appropriation requests to investment program positions, and for assigning variants to plan versions. This method works with buffering. This means that, in the same LUW,additional methods can change the data that was created and/or changedby this method, or other instances, without prior updating being necessary.
The relationship between the import parameters Language and LanguageISO is as follows: If the Language import parameter is filled, then the LanguageISO import parameter is ignored. If the Language import parameter is not filled, then the system uses
the value of the LanguageISO import parameter. Ifneither of the two import parameters is filled, then the logon language is used as a default. Using this method, it is not possible to create more than one variant for the newly created appropriation request. Use the
AppropriationRequest.AddVariant method for creating additional variants. For information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation alsodeals in detail with the use of the parameters and their limitations.
Messages are returned in the parameter return. The parameterdocumentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library.
For more information, refer to Investment Programs in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
Delete
The AppropriationRequest.Delete deletes an appropriation request. NotesTo use this method, you need authorization for deleting appropriation requests. This method works with buffering. This means that, in the same LUW,
additional methods can change the data that was created and/or changedby this method, or other instances, without prior updating being necessary. Using this method, it is not possible to delete individual variants of an appropriation request. You can use the
AppropriationRequest.RemoveVariant method for deleting variants. For information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation alsodeals in detail with the use of the parameters and their limitations.
Messages are returned in the parameter return. The parameterdocumentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
GetDetail
The AppropriationRequest.GetDetail method returns all data of anappropriation request. This data includes: the master data of theappropriation request and all of its variants, the plan values of allof its variants, data on the assignment of variants to versions, and data on assignment to investment programs.
NotesTo use this method, you need display authorization for approriationrequests and variants, and display authorization for the plan values of a variant. This method takes into account changes made in the buffer by BAPIs (for
creating or changing) of the same business object type, but where the changes were not yet updated. The relationship between the import parameters Language and LanguageISO is as follows: If the Language import parameter is filled, then the LanguageISO
import parameter is ignored. If the Language import parameter is not filled, then the system usesthe value of the LanguageISO import parameter. Ifneither of the two import parameters is filled, then the logon language is used as a default.
Using this method, it is not possible to obtain information on thesystem status or user status of the appropriation request or thevariants of the appropriation request. For these activities you use the AppropriationRequest.GetStatus method.
For information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation alsodeals in detail with the use of the parameters and their limitations. Messages are returned in the parameter return. The parameter
documentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
GetStatus
The AppropriationRequest.GetStatus method returns the systemstatus and user status of the appropriation request and its variants. NotesTo use this method, you need display authorization for the appropriation request and its variants.
This method takes into account changes made in the buffer by BAPIs (forcreating or changing) of the same business object type, but where the changes were not yet updated. The relationship between the import parameters Language and LanguageISO is as follows:
If the Language import parameter is filled, then the LanguageISO import parameter is ignored. If the Language import parameter is not filled, then the system usesthe value of the LanguageISO import parameter. If
neither of the two import parameters is filled, then the logon language is used as a default. For information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation alsodeals in detail with the use of the parameters and their limitations.
Messages are returned in the parameter return. The parameterdocumentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
RemoveVariant
The AppropriationRequest.RemoveVariant method deletes a variant of an appropriation request. NotesTo use this method, you need change authorization for the appropriationrequest and for the variant to be deleted. In addition, the user status of the variant being deleted has to allow deletion.
This method works with buffering. This means that, in the same LUW,additional methods can change the data that was created and/or changedby this method, or other instances, without prior updating being necessary. Using this method, it is not possible to delete the last or only variant of an appropriation request.
Other methods for working with variants include: AppropriationRequest.AddVariantAppropriationRequest.ChangeVariantAppropriationRequest.AssignVariantToVersionAppropriationRequest.UnAssignVariantVersion
AppropriationRequest.SetPlanValuesAppropriationRequest.ResetPlanValueFor information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation also
deals in detail with the use of the parameters and their limitations. Messages are returned in the parameter return. The parameterdocumentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
ResetPlanValue
The AppropriationRequest.ResetPlanValue method resets the planvalues of an appropriation request variant back to zero. NotesTo use this method, you need change authorization for the appropriationrequest and for the variant, as well as authorization for maintaining plan values for the variant.
This method works with buffering. This means that, in the same LUW,additional methods can change the data that was created and/or changedby this method, or other instances, without prior updating being necessary. Using this method, it is not possible to physically delete the plan values of a variant.
To change plan values of an appropriation request variant, use the AppropriationRequest.SetPlanValues method. For information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation also
deals in detail with the use of the parameters and their limitations. Messages are returned in the parameter return. The parameterdocumentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
SetPlanValues
The AppropriationRequest.SetPlanValues method changes the plan values of an appropriation request variant. NotesTo use this method, you need change authorization for the appropriationrequest and the variant, as well as authorization for maintaining plan values for the variant.
This method works with buffering. This means that, in the same LUW,additional methods can change the data that was created and/or changedby this method, or other instances, without prior updating being necessary. Using the AppropriationRequest.ResetPlanValue method, you can
reset the plan values of an appropriation request to zero. For information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation alsodeals in detail with the use of the parameters and their limitations.
Messages are returned in the parameter return. The parameterdocumentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
UnAssignExpenditureProgPos
The AppropriationRequest.UnAssignExpenditureProgPos methodcancels the assignment of an appropriation request to one or more investment program positions. NotesTo use this method, you need change authorization for appropriation
requests. You also need authorization for editing assignments to program positions. This method works with buffering. This means that, in the same LUW,additional methods can change the data that was created and/or changedby this method, or other instances, without prior updating being necessary.
Using the AppropriationRequest.AssignToExpenditureProgPosmethod, you can assign an appropriation request, which is not yetassigned, to one or more investment program positions. To change anexisting assignment to one or more investment program positions, you can use the
AppropriationRequets.ChangeAssignmentExpProgPos method. For information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation alsodeals in detail with the use of the parameters and their limitations.
Messages are returned in the parameter return. The parameterdocumentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library.
For more information, refer to Investment Programs in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|
UnAssignVariantVersion
The AppropriationRequest.UnAssignVariantVersion method removesthe assignment of an appropriation request variant to one or more plan version(s). NotesTo use this method, you need change authorization for the appropriation
request and the variant. In addition, you need authorization forversion assignment on the appropriation request, on the variant, and on the approval level of the plan version. This method works with buffering. This means that, in the same LUW,
additional methods can change the data that was created and/or changedby this method, or other instances, without prior updating being necessary. Using the AppropriationRequest.AssignVariantToVersion method,you can assign an appropriation request variant to one or more plan versions.
For information on the data being transferred, see the documentationfor the individual parameters of the method. This documentation alsodeals in detail with the use of the parameters and their limitations. Messages are returned in the parameter return. The parameter
documentation shows the return codes and their meanings. Further InformationFor more information, refer to Appropriation Requests in the SAP Library.
|
|
|
|
11-Dec-2005
|
|
|
|
|