CLEAR SY-BINPT is not POSSIBLE

Hi everyone
I need to do 'call transaction using' with parameter nobinpt = space and mode = 'E'
But when we entry in the transaction values of is sy-binpt = 'X' (params-nobinpt doesn' t works)
I try to do 'Clear sy-binpt' in the transaction but doesn' t works also
I read some answers about this question and it doesn´t works also
Thanks in advance

hi Zaplana,
Don't change system variables!
you have to declare a work area type CTU_PARAMS and change the value there. Than you have to do like this:
CALL TRANSACTION
OPTION FROM you_work_area
hope this helps
ec

Similar Messages

Clearing of Account is not possible ..................?

Hi All,
Clearing of Account is not possible for such entries where Business Place/ Section Code is Blank.How to track those transactions (without Business Place/Section code) and to make transactions for clearing these Accounts...
Please help to solve my problem...
Thanks
Mousumi Pandey

Dear Pandey,
some body has done the validation for business place by using Accounting key " K"
you can track the business place by suing FBL5N and FBL1N FBL3N (IN ECC - 6 - FAGLL03) and changes the lay out Business Place and Section Code.
you can find the line item with or with out B P and Sec Code.
regards
radha

Profit Center Clearing Account Line Item not possible to display ?

Hi
All Experts ,
I want to see the line items for Profit Center clearing account ( Zero Balancing ) in FS10N but after double clicking in system
shows no line item possible for this account.
Please suggest some T.codes or reports through which I can see line items for Profit Center clearing account.
Is there any different configurations made for Profit center clearing account ?
Regards,
Sharvari.
Edited by: Sharvari Joshi on Jul 18, 2009 2:27 PM
Edited by: Sharvari Joshi on Jul 18, 2009 2:32 PM

Dear Sharvari,
You are not able to see line items because "line items" field in master record must not have been selected. To check it goto
FS00, enter your GL account. For documents which have already been posted, you will not be able to see line items even after selecting Line Item in master record.
To veiw the line item record for this GL account use table BSEG in SE16.
Regards,
Chintan Joshi.

KO88:Not possible to post down payment clearing. There are no down payments

Hi,
We are doing Full Settlement of an order in TCode KO88. There are few Down payments against a PO. Initially, system gave an error as follows: -
You cannot post comp.retirement for asset 120002 0 with this trans.type
    Message no. AA341
Diagnosis
    A down payment was posted to asset 120002 0. In depreciation area 01, if
    not elsewhere, all down payments were not cleared.
Procedure
    Before posting a complete retirement on this asset, you have to first
    clear the down payment in all depreciation areas.
We cleared the down payments and ran KO88 again, but a new error popped as given below.
Not possible to post down payment clearing. There are no down payments.
    Message no. AA571
Any help will be acclaimed.
Regards,
CMC Team
Edited by: CMC Team on Jan 18, 2012 2:59 PM
Edited by: CMC Team on Jan 18, 2012 3:01 PM

Friend,
Probably you did not take the trouble to search the SAP Oss for notes on this error message.
Please search for 'AA571' in the notes section of SAP oss and you will find several notes addressing the exact issue you are having.
For your convenience.
www.service.sap.com/notes
Best regards,
Vishal Thakur.

Not possible to post down payment clearing. There are no down payments:CJ88

Hi Experts,
When I settle WBS Element cost to the Asset Under Construction using transaction CJ88, I receive following error.
AA571 Not possible to post down payment clearing. There are no down payments.
Please help.
Thank You.

Hi,
first please check if the message AA 571 is right:
- Please check table ANLC. If ANLC-KANZA + ANLC-ANSAZ < 0    AA 571
- Check asset values (AW01N, ANEP, ANLC) and find out where the negative down payments come from (tty 180, 181)
However, in some cases a negative down payment balance cannot be avoided (for example through translation differences in foreign currency areas). This is the problem of AA 571. Sometimes it is not justified. For this
cases we have the following note:
860038 Error AA571 not justified
Using SM30, for the T100S table, create an entry for the message
class AA, message number 571, allowed message type "AEW" and
standard message type "E". Select the entry as 'Switch off'.
If when you post to a fixed asset the down payments are negative, or
become negative through the posting, you continue to receive an error as
a default with these changes.
Recommended procedure:
o Change this message to a warning message for one or several
       special users. This user should then be used to post to any such
       fixed asset that has down payments that are already negative or
       become negative through posting.
o This should only be permitted in the cases where a negative down
       payment balance cannot be avoided due to foreign currency
       rounding.
regards Bernhard
Edited by: Bernhard Kirchner on Feb 11, 2011 9:27 AM

Error: Not possible to post down payment clearing.There are no down payment

Hi expert,
I am running a settlement for an internal order and encounter the following error message.
"Not possible to post down payment clearing. There are no down payments."
Message no. AA571
When checked on the vendor, the invoice has been cleared in the same month before the settlement. Under the Internal order line items, there is still an unsettled amount of the invoice.
This internal order settles to an AUC asset. Previous month settlement was ok. Only problem with december.
The downpayment acct is currently zero.
Is there something wrong with the message table, or the posting of the vendor invoice ? Anything to do with the special GL indicator ?
Kindly advise what is the cause and the method to resolved this asap.
Thanks.
Angel.

Hi Angel ,
My client also getting error message while doing settlement(T.C.KO88) even though Note.8600038 applied.
Error Message:Not Possible to post down payment clearing .There are no down payments.
Message: AA571
If your issue is solved.
please can you tell how did you solve this issue.
Thanks,

FBRA-Document includes already cleared items - reversal not possible

While reset and reversal using FBRA I am getting the following error. Please do let me know if any clue to resolve this issue.
Document includes already cleared items - reversal not possible
Message no. F5 308
Diagnosis
A reverse posting clears all line items that are managed as open items. This is not possible if one of the items in question has already been cleared by another method.
System Response
Error message.
Procedure
If you really want to reverse the document with the number you specified, display the cleared items and reset all those items for which you can find clearing document numbers. Then repeat the reverse transaction.

Hi Dewang,
Thanks for your quick responce.
step 01- Posted Customer Invoice on 01-Jan-2011with RV doc with Rs-1200: Doc 111111
Step 02- Posted Customer downpayment on 01-Jan-2011 with DZ doc with Rs-1200: Doc No 2222222
Step 03- Clear Customer line items on 10-Jan-2011 with AB doc with Doc no- 3333333
Trying to reverse Cleared Item (i.e. Doc No 3333333) with T-Code FBRA. While doing Reset and reversal we are getting the above problem.
Please let me know if you need any information.
Regards
Raj

Document is alrady contains cleared items-reversal not possible

Hi All,
At the time of MIRO reversal we are getting error massage Document is already contains cleared items-reversal not possible
actually one MIRO document using TDS line item and we make a payment for that TDS line item after that we try to reserve MIRO document that time we are getting error massage.
Please help me to resolve this issue.
Regards,
juhi

Hi Spradip & Minesh,
Thanks
But as per my client they do the same in system but this document only not getting reveres why they don't know.
but what we do because they want to reverse the document.
Please help me
Thanks & Regards,
Juhi

MR8M-Document already contains cleared items - reversal not possible

Hi Gurus,
I am getting error message Document XXXXX 1000 2014 already contains cleared items - reversal not possible while cancelling IR via Tcode MR8M.
Invoice was already paid twice by mistake hence we are trying to cancel via MR8M.
I know we can do via FBRA by resetting the cleared item but is there any other options or workaround?
Thanks,
Kumar

Hi Jurgen,
Thanks for your reply;
Invoice posted twice and 1 needs to be reversed. Please refer the attached screenshot.
Thanks,

E not possible to post down payment clearing.

Dear all sap guru's
iam getting this meg:
could you explaine me?
document XXXX E not possible to post down payment clearing. there are no downpayment.
regs
laks

Hi Lakshmi,
Give some clarity for your issue.
Which t.code ur using
and check it downpayment is in the open item or not.
giv me the reply i will update you

I know this is supposedly not possible, but I need to retrieve a specific voicemail from my iPhone which was also "cleared" from the Deleted Messages box. Any suggestions?

I know this is supposedly not possible, but I need to retrieve a specific voicemail from my iPhone which was also "cleared" from the Deleted Messages box. Any suggestions?
This is highly important. I know the number from which the voicemail arrived, but have not been able to figure out how to retrieve it. I accidentally had the voicemail in the Deleted Messages folder, and then Cleared this folder. If there is any possible way I might be able to retrieve this message, even if there is a cost associated with it, please help me.
Thank you.

I think you maybe able to restore from backup if that voicemail was included in the backup. http://support.apple.com/kb/HT1766

Not possible to reverse the document in financial accounting Error

Hi All
We are getting invoice Data from Client
through ACC_EMPLOYEE_PAY02
Document Like
31 45699(vendor )    2356.00
31 45688 (vendor)    1245.00
31 45677 (vendor)    1000.00
31 45666 (vendor)    2000.00
40 Accur(Clearing)       6601.00
In this list some of vendors i did payment Run.
I need to reverse the 1 vendor open Item.
It is showing open item but i am unable to reverse this document.
i tried to FB03 but it is showing Below Error
Not possible to reverse the document in financial accounting
Message no. F5673
Diagnosis
Document '1900000003' in company code '1164' should be reversed. However,
this document was not posted in the Financial Accounting module, HRPAY is, rather, of type ''.
System Response
Documents which were not originally posted in Financial Accounting also cannot be reversed in Financial Accounting.
Procedure
Reverse the original transaction.
You can display the original document from the FI document via 'Environment' -> 'Original doc.'.
I tried to trace Original Document.
trhough Environment -> Original Doc.
ERROR is
Payroll Posting Document 000000091 does not exist
How to Reverse the Open Item.
raju.

Hi,
SAP doesn't allow you to reverse a document in FI if it was created subsequently from another module (in your case HR).
Why don't you use F-44 transaction code to manually clear the open vendor line item and offset it against the same clearing account?
Regards

Error - GR reduction not possible in MIRO (Message no. FICUSTOM350)

Hello Gurus,
I am getting error while doing MIRO (GR reduction not possible. Wrong cmmt item (fin. trans. 30) in GR/IR acct) .
I have activated FM - BCS. In Customizing transaction OFUP (Make other settings) I have ticked GR and INV and my update profile is 000101 (Payment budget; Payment basis ; Posting date).
I have created a commitment item for GR/IR specific and assigned financial transaction 40 then also system is giving the same error. The issue is system is not creating a FM line item for GR/IR clearing account at the time of MIGO but only creating for P&L item (Debit Part). Now when we post MIRO system is looking for FM line item for GR/IR (which should have been created during MIGO) for clearing hence error appears.
Please let me guide if I have missed some configuration or have done some wrong configuration.
Full Error description is :
GR reduction not possible. Wrong cmmt item (fin. trans. 30) in GR/IR
acct
Message no. FICUSTOM350
Diagnosis
You are trying to reduce a goods receipt line (GR) with an invoice (IR).
However, the GR/IR clearing account has an incorrect financial transaction ('30'
instead of '40') in the commitment item.
System Response
The system cannot calculate a GR reduction. This is not a program error, but
rather an inconsistency in the customer master.
In order to calculate the GR reduction, Funds Management (FM) updating has to
create original records for the GR lines with value type '54' and transaction
'RMWE'. Otherwise it is not possible to calculate the reduction.
Procedure
Correct the commitment item of the GR/IR clearing account. If necessary,
reconstruct the document in FM.
Regards
Rohit

Hi,
Sorry, I have a question about message FICUSTOM350. I also encounter this error message when we do MIRO and set the AP amount = 0. I try to set GR/IR as '40' but I found GR/IR account will not determint through FMDERIVE. I found this seems the standard behave in SAP. So, I close the message FICUSTOM350 and MIRO is work OK without error. But when I execute the report FMRP_RFFMEP1AX , the budget is incorrect. The system does not reduce the payment budget. Ex: PO amount = 7000 USD, MIRO AP amount =0 , I think the total budget should be 0, but the total payment budget of the report is 7000. Please advise.
Thanks and Best Regards,

SSFCOMPOSER - 154 - No output request open. End not possible.

Hi Experts,
I'm trying to print multiple smartforms using FMs SSF_OPEN and SSF_CLOSE. Inside the main program RBDAPP01 (Inbound processing for IDOCS) there is a loop at the IDOCS to be processed. Deep within the processing, we have a custom FM being called which prints smartforms. Since there is a loop at the calling main program, I have organized the code in the custom FM such that the first IDOC calls SSF_OPEN and the last IDOC calls SSF_CLOSE, so that all IDOCS in between will be able to print their smartforms. Here is the call stack:
8
SAPLZCUSTOM
ZCUSTOMPROGRAM
113
FUNCTION
ZCUSTOMPROGRAM
7
SAPLPPC1
ZCUSTOMPROGRAM
136
FUNCTION
KK2A_GET_DATA_FROM_IDOC
7
SAPLPPC1
LPPC1U01
1
FUNCTION
KK2A_GET_DATA_FROM_IDOC
6
SAPLBD20
LBD20F0A
454
FORM
IDOCS_PASS_TO_APPLICATION
5
SAPLBD20
LBD20F0B
69
FORM
IDOCS_PROCESS
4
SAPLBD20
LBD20U05
260
FUNCTION
IDOC_INPUT
3
SAPLEDIR
LEDIRU02
182
FUNCTION
IDOC_START_INBOUND
2
SAPLBD12
LBD12U04
37
FUNCTION
APPLICATION_IDOC_POST_IMMEDIAT
1
RBDAPP01
RBDAPP01
388
EVENT
START-OF-SELECTION
The problem is:
1. When I only have 1 IDOC being processed, SSF_OPEN and SSF_CLOSE happens in the custom FM at the same time. This creates a successful spool.
2. Whereas, when I have 2 or more IDOCS, SSF_OPEN happens in the first IDOC, but then it goes back to the calling program, and then when the last IDOC is encountered SSF_CLOSE is called. The FM SSF_CLOSE in this scenario calls the exception INTERNAL_ERROR (sy-subrc = 2).
The system message is SSFCOMPOSER - 154 - No output request open. End not possible.
Why is this happening? Is it because that other programs (calling programs) may have affected the status of SSF_OPEN? It seems that the SSF_OPEN is no longer open.
Thanks in Advanced,
Jack

No, it will not hold the smartform open, but you don't need to hold it open in order for printout to be accumulated in one spool. Spool system does the accumulation automatically, provided the spool requests that are to be added to an existing spool request are:
- generated in the same transaction and
- have the same attributes (such as user, title, output device, client from which the request was issued, number of copies, priority, cover sheet setting, archive mode, and ABAP session number).
Important is: where do OUTPUT_OPTIONS like printer come from currently? Is print parameters popup displayed on first Idoc for user to choose printer and options? Or do you use USER_SETTINGS = 'X' to simply take over defaults from user master? If the print options dialog is displayed, it needs to be controlled as well so it's displayed only once.
Assuming print options come from the user in dialog, the logic without explicit open/close could look somewhat like this:
On first idoc:
- call SSF_OPEN importing JOB_OUTPUT_OPTIONS to display print options dialog; move-corresponding JOB_OUTPUT_OPTIONS to global OUTPUT_OPTIONS;
- set OUTPUT_OPTIONS-TDNEWID = 'X' and clear OUTPUT_OPTIONS-TDFINAL, to ensure new spool will be started (overriding user choices for these parameters!);
- if the user has set OUTPUT_OPTIONS-TDIMMED = 'X' save it globally and clear it;
- set CONTROL_PARAMETERS-NO_OPEN = 'X';
On subsequent idoc:
- clear OUTPUT_OPTIONS-TDNEWID;
- clear CONTROL_PARAMETERS-NO_OPEN;
On last idoc:
- set OUTPUT_OPTIONS-TDFINAL = 'X' (this is not absolutely necessary, but prevents further appending to the spool);
- restore OUTPUT_OPTIONS-TDIMMED from the value saved on first idoc;
Calling Smartform:
- set CONTROL_PARAMETERS-NO_DIALOG = 'X';
- call smartform passing OUTPUT_OPTIONS and CONTROL_PARAMETERS;
The logic is somewhat complicated; I'd wrap it in a class (singleton, which would be de-instantiated after last idoc) to avoid global data and code other than simple method call(s) in FM.
Even if you decide to refactor the logic, it would still be important to understand, I think, why the current logic does not work (where and why smartform gets closed)... Maybe there are some nasty "surprises" somewhere, and your current algorithm should work.
cheers
Janis

Dump - Access using NULL object reference is not possible!!!

Hi,
I'm using the BCS class for sending HTM format email so i use the below code for that its working,
DATA: gr_document      TYPE REF TO cl_document_bcs,
gr_document = cl_document_bcs=>create_document(
                      i_type    = 'HTM'
                       i_text    = t_html
                       i_importance = '5'
                       i_subject = gc_subject ).
Next task is to send the image so i'm creating an another object to the same class, below code
*Image from MIME
DATA: o_mr_api         TYPE REF TO if_mr_api.
DATA is_folder TYPE boole_d.
DATA l_img1 TYPE xstring.
DATA l_img2 TYPE xstring.
DATA l_loio TYPE skwf_io.
DATA: lo_document   TYPE REF TO cl_document_bcs.
IF o_mr_api IS INITIAL.
   o_mr_api = cl_mime_repository_api=>if_mr_api~get_api( ).
ENDIF.
CALL METHOD o_mr_api->get
   EXPORTING
     i_url              = '/SAP/PUBLIC/ZDEMO/tick.png'
   IMPORTING
     e_is_folder        = is_folder
     e_content          = l_img1
     e_loio             = l_loio
   EXCEPTIONS
     parameter_missing = 1
     error_occured      = 2
     not_found          = 3
     permission_failure = 4
     OTHERS             = 5.
CALL METHOD o_mr_api->get
   EXPORTING
     i_url              = '/SAP/PUBLIC/ZDEMO/Delete.png'
   IMPORTING
     e_is_folder        = is_folder
     e_content          = l_img2
     e_loio             = l_loio
   EXCEPTIONS
     parameter_missing = 1
     error_occured      = 2
     not_found          = 3
     permission_failure = 4
     OTHERS             = 5.
*Convert XSTRING to ITAB
DATA :lt_hex1 TYPE solix_tab,
       lt_hex2 TYPE solix_tab,
       ls_hex LIKE LINE OF lt_hex1,
       lv_img1_size TYPE sood-objlen,
       lv_img2_size TYPE sood-objlen.
CLEAR : lt_hex1, lt_hex2, ls_hex, lv_img1_size, lv_img2_size.
WHILE l_img1 IS NOT INITIAL.
   ls_hex-line = l_img1.
   APPEND ls_hex TO lt_hex1.
   SHIFT l_img1 LEFT BY 255 PLACES IN BYTE MODE.
ENDWHILE.
WHILE l_img2 IS NOT INITIAL.
   ls_hex-line = l_img2.
   APPEND ls_hex TO lt_hex2.
   SHIFT l_img2 LEFT BY 255 PLACES IN BYTE MODE.
ENDWHILE.
*Findthe Size of the image
DESCRIBE TABLE lt_hex1 LINES lv_img1_size.
DESCRIBE TABLE lt_hex2 LINES lv_img2_size.
lv_img1_size = lv_img1_size * 255.
lv_img2_size = lv_img2_size * 255.
*Attach Images
clear: lo_document.
lo_document->add_attachment(
   EXPORTING
     i_attachment_type     = 'png'                  " Document Class for Attachment
     i_attachment_subject = 'img1'                " Attachment Title
     i_attachment_size     = lv_img1_size           " Size of Document Content
     i_att_content_hex     = lt_hex1 " Content (Binary)
lo_document->add_attachment(
   EXPORTING
     i_attachment_type     = 'png'                  " Document Class for Attachment
     i_attachment_subject = 'img2'                " Attachment Title
     i_attachment_size     = lv_img2_size           " Size of Document Content
     i_att_content_hex     = lt_hex2 " Content (Binary)
but it throws the dump " Access using NULL object reference is not possible" when i tries to access for method add_attachment...
Thanks,
Siva

Yes there is commit work after that, Below code
      gr_document = cl_document_bcs=>create_document(
                       i_type    = 'HTM'
                        i_text    = t_html
                        i_importance = '5'
                        i_subject = gc_subject ).
*Image from MIME
DATA: o_mr_api         TYPE REF TO if_mr_api.
DATA is_folder TYPE boole_d.
DATA l_img1 TYPE xstring.
DATA l_img2 TYPE xstring.
DATA l_loio TYPE skwf_io.
DATA: lo_document   TYPE REF TO cl_document_bcs.
IF o_mr_api IS INITIAL.
   o_mr_api = cl_mime_repository_api=>if_mr_api~get_api( ).
ENDIF.
CALL METHOD o_mr_api->get
   EXPORTING
     i_url              = '/SAP/PUBLIC/ZDEMO/tick.png'
   IMPORTING
     e_is_folder        = is_folder
     e_content          = l_img1
     e_loio             = l_loio
   EXCEPTIONS
     parameter_missing = 1
     error_occured      = 2
     not_found          = 3
     permission_failure = 4
     OTHERS             = 5.
CALL METHOD o_mr_api->get
   EXPORTING
     i_url              = '/SAP/PUBLIC/ZDEMO/Delete.png'
   IMPORTING
     e_is_folder        = is_folder
     e_content          = l_img2
     e_loio             = l_loio
   EXCEPTIONS
     parameter_missing = 1
     error_occured      = 2
     not_found          = 3
     permission_failure = 4
     OTHERS             = 5.
*Convert XSTRING to ITAB
DATA :lt_hex1 TYPE solix_tab,
       lt_hex2 TYPE solix_tab,
       ls_hex LIKE LINE OF lt_hex1,
       lv_img1_size TYPE sood-objlen,
       lv_img2_size TYPE sood-objlen.
CLEAR : lt_hex1, lt_hex2, ls_hex, lv_img1_size, lv_img2_size.
WHILE l_img1 IS NOT INITIAL.
   ls_hex-line = l_img1.
   APPEND ls_hex TO lt_hex1.
   SHIFT l_img1 LEFT BY 255 PLACES IN BYTE MODE.
ENDWHILE.
WHILE l_img2 IS NOT INITIAL.
   ls_hex-line = l_img2.
   APPEND ls_hex TO lt_hex2.
   SHIFT l_img2 LEFT BY 255 PLACES IN BYTE MODE.
ENDWHILE.
*Findthe Size of the image
DESCRIBE TABLE lt_hex1 LINES lv_img1_size.
DESCRIBE TABLE lt_hex2 LINES lv_img2_size.
lv_img1_size = lv_img1_size * 255.
lv_img2_size = lv_img2_size * 255.
*Attach Images
create object lo_document type cl_document_bcs.
lo_document->add_attachment(
   EXPORTING
     i_attachment_type     = 'png'                  " Document Class for Attachment
     i_attachment_subject = 'img1'                " Attachment Title
     i_attachment_size     = lv_img1_size           " Size of Document Content
     i_att_content_hex     = lt_hex1 " Content (Binary)
lo_document->add_attachment(
   EXPORTING
     i_attachment_type     = 'png'                  " Document Class for Attachment
     i_attachment_subject = 'img2'                " Attachment Title
     i_attachment_size     = lv_img2_size           " Size of Document Content
     i_att_content_hex     = lt_hex2 " Content (Binary)
       "Add document to send request
       CALL METHOD gr_send_request->set_document( gr_document ).
       TRY.
         CALL METHOD gr_send_request->SET_SEND_IMMEDIATELY
           EXPORTING
             I_SEND_IMMEDIATELY = 'X'.
*    CATCH CX_SEND_REQ_BCS INTO BCS_EXCEPTION .
**Catch exception here
       ENDTRY.
       DATA: LO_SENDER TYPE REF TO IF_SENDER_BCS VALUE IS INITIAL.
       TRY.
         LO_SENDER = CL_SAPUSER_BCS=>CREATE( SY-UNAME ). "sender is the logged in user
* Set sender to send request
         gr_send_request->SET_SENDER(
         EXPORTING
         I_SENDER = LO_SENDER ).
*    CATCH CX_ADDRESS_BCS.
****Catch exception here
       ENDTRY.
       "Send email
       CALL METHOD gr_send_request->send(
         EXPORTING
           i_with_error_screen = 'X'
         RECEIVING
           result              = gv_sent_to_all ).
       IF gv_sent_to_all = 'X'.
         WRITE 'Email sent!'.
       ENDIF.
       "Commit to send email
       COMMIT WORK.
       "Exception handling
     CATCH cx_bcs INTO gr_bcs_exception.
       WRITE:
         'Error!',
         'Error type:',
         gr_bcs_exception->error_type.
   ENDTRY.

CLEAR SY-BINPT is not POSSIBLE

Similar Messages

Maybe you are looking for