Use of field 'Payment Considered To' in Dunning Proposal (FPVA)

Hi all,
May I know what is the purpose of the field 'Payment Considered To' in FPVA? Let say I want to issue dunning dated 08 March 2010 (backdated). Can I use this field to limit the payment received by us until 08 March 2010? What if the payment received after that date (for example 16 March 2010)? Can the document still considered outstanding at 08 March 2010? What if I left the field blank? What it will take?
Thanks,

Hello,
In case of payment order, the open item is marked as paid with the payment order number but the clearing entry is not made until the bank file is uploaded. The date may be given there so that it is indicated in the dunning letter as an information to the business partner. Usually only the current date may be indicated there. If no date is entered in that field then all the payments will be considered and no date will be printed in the dunning letter.
I hope this reply clarifies your question
Regards
Venkat

Similar Messages

Error in ECC6.0 - Dunning Proposal - FPVA

Hi SAP Expert
I had executed Dunning Proposal - FPVA. I was hit the error message from system said "There are no internal numbers which have not been assigned".
I go into SNUM but I couldn't find the number range object for Dunning Proposal. May I know where I can define for internal numbers in order to execute the Dunning Proposal - FPVA? Which object I should refer to ?
Million thanks.
Regards
Jacky

Jacky,
Go through the SAP note 732878.
You need to maintain number ranges in SNUM for object id EMMA_RUNID.
The above config is for all mass programs in FICA i.e FPVA, FPVB, FPY1, FPMA etc
Hope this helps
Rgds
Rajendra

Payment run (FPY1) and Dunning proposal Run (FPVA) not gettting executed

Dear All IS-U genius people,
When i am running the FPY1(payment run) and FPVA (Dunning proposal Run), i am getting following error:
C Interval from 0000000021 to ZZZZZZZZZZ MAHN20070712TST14 (in dunning run)
and
C Interval from 0000000021 to ZZZZZZZZZZ PAYP20070710TST01 (in Payment run)
I have seen that the Mass number ranges are there and properly assigned to the Document types.
Please help me to solve this error.
Regards,

Hello,
perhaps, I don't exactly understand, where the error is. The message
C Interval from 0000000021 to ZZZZZZZZZZ MAHN20070712TST14
is normally just an information message to tell you what range of business partners is processed. A mass activity always uses ALL possible numbers to build the intervals. During the run, the intervals are adjusted to existing values, as I described before -> the limits of this intervals are written to application log. But it is nomally not the range of really processed objects. If you have the possibility to restrict the selection of business partners (see FPY1, first tabstrip), then this selection is mixed up with built intervals (see function module FKK_DI_INTERVAL_INTERSECTION). Only the objects, that are in your selection are processed within a given interval.
Do you have a selection for business partners e.g. on the first tabstrip of FPY1? Are not all business partners processed you want to be processed?
Regards, Marina

Dunning Proposal-FPVA

Dear Experts,
I am doing the dunning proposal, when i have checked in the application log there is no dunning notices in the dunning proposal.
I am getting the message "Dunning Notices in Dunn. Prop. 0". There is no incoming payment method and lock in the contract account master data.
Could anyone give some idea please?
Thanks & Regards,
Aswin

Hi Amlan,
1. I have checked the dunning history table there is no item in that table.
2. I have activated the "additional info" i am getting below listed messages. But I am not able to get any info relevant to the error.
ID     No.     Message Text
EMMA     11     Start business process Dunning Proposal for Business Partner 2082
>3     226           1 dunning group(s) created
>3     346           No dunnable items in dunning group
EMMA     11     Start business process Dunning Proposal for Business Partner 2082
>3     226           1 dunning group(s) created
>3     346           No dunnable items in dunning group
>3     535     FICA Dunning Proposal Run
>3     535     22.05.2011 73
>6     372     Computer sapsbx, job name MAHN2011052273_001, job count 13060101
>3     248     Job no. 001, reconciliation key 1114273   AA
>6     378     Job started as update run
>6     354     Mass activity started: Interval 1 from 0000000001 to ZZZZZZZZZZ, activity type MAHN
0     18     COMMIT successful
MASSACT     101     Selected Item Groups         1
MASSACT     101     Selected Items         1
MASSACT     102     Accounts with Dunning Lock 0
MASSACT     102     Accounts with Posting Lock 0
MASSACT     101     Dunning Groups to be Checked         1
MASSACT     102     Groups w/o Main Receivable 0
MASSACT     102     Dunning Notices in Dunn. Prop. 0
Thanks
Aswin

When is a message considered as received when using Near Field Communication?

Hi there!
I'm using Near Field Communication(NFC) in my app(it's a game) and I just want to send very simple messages so the regular NFC tap suffices.
I've read the documentation and went through the proximity sample and I understand what I've to do to make this work, so no problems so far.
The thing I'm struggeling with is the following: I would like to send a message using NFC to a particular player in my game.
Two players are connected to each other and only those two should be supposed to be able to send messages to each other using NFC.
These messages do not contain any secret information so I can use the "Windows." format as tag to subscribe to and send messages with.
I came up with the idea to subscribe for a tag that's basically your userId and publish messages with a tag that consists out of your opponents user_id. All of that works fine the thing is, I use the MessageTransmitedHandler and MessageReceivedHandler, the
one is raised when you've succesfully transmited the message and the other one when you've received a message.
These callback functions make sure that you only send a message once and receive it once by using the StopPublishingMessage and StopSubscribingForMessage functions. And here's the catch, I only want to call these functions if you actually "consume"
the message you receive! And stop publishing a message when the correct opponent received it.(This is to make sure that if multiple users are in the same room for example that only the one's related to each other can tap each other's devices).
Right now the callback function will always stop publishing the message, or subscribing to a message even if you tapped the wrong user.
I'm not 100% sure but I do believe this is because the callback function is called no matter if the other device really "consumed' the message.
So my question is, is there a way to determine if the opposing side actually "consumed' the message? If there's no built in function for this(which I think there isn't after I went through the documentation) do you guys have any idea how I could achieve
the behaviour I want?
I hope my message isn't too confusing, if it's feel free to indicate that and I'll try to clarify those parts.
Thanks in advance!
My best regards
Jan

Proximity is a great way for users on tow devices to share your app experience and data. You can establish a connection between two peer apps at one time as I know. This quickstart describe it in detail,
https://msdn.microsoft.com/en-us/library/windows/apps/xaml/hh465205.aspx. If one user want to communicate with a third user, his app need to connect to that one first.
If I'm not mistaken this sets up a WiFi or Bleutooth connection, I'm not really looking for that since the message I wish to send is really really short and NFC is perfect for it. It seems like a hassle to me to set up such a peer to peer connection just to
be able to identify if the message has been received by the correct user.

Payment Advice Generation during Dunning

Hi - we are on ECC6.0 and I have noticed in the dunning table MHNK that there is a field for payment advice. Does anyone know how to generate a payment advice from the dunning run that can be printed on the form and then referenced when the customer sends a payment?
Thanks, Alisa

hello
go to f110 screen
enter rundate and identification used.
then this will be displayed ( if run already carried out)
Parameters have been entered
Payment proposal has been created
Payment run has been carried out
Posting orders: xx generated , xx completed.
click printout button which is next to proposal button.
then choose start immediate option and give a job name.
then got to sm37 and you will find the job.
once the job is finished go to spool .you will find spool button on sm37 screen.
click on spool.
you can print the advices now.
hope this solves the problem

ALV report using the field catalog

which is the quickest way to generate an ALV report using the field catalog merge. without needing to build the field catalog manually .
is it easier to create a structure and passe it in the field catalog merge . if yes can i have an example plzzzz

hI
Supports the creation of the field catalog for the ALV function modules
based either on a structure or table defined in the ABAP Data
Dictionary, or a program-internal table.
The program-internal table must either be in a TOP Include or its
Include must be specified explicitly in the interface.
The variant based on a program-internal table should only be used for
rapid prototyping since the following restrictions apply:
o Performance is affected since the code of the table definition must
always be read and interpreted at runtime.
o Dictionary references are only considered if the keywords LIKE or
INCLUDE STRUCTURE (not TYPE) are used.
If the field catalog contains more than 90 fields, the first 90 fields
are output in the list by default whereas the remaining fields are only
available in the field selection.
If the field catalog is passed with values, they are merged with the
'automatically' found information.
Below is an example ABAP program which will populate a simple internal table(it_ekpo) with data and
display it using the basic ALV grid functionality(including column total). The example details the main
sections of coding required to implement the ALV grid functionality:
                         Data declaration
                         Data retrieval
                         Build fieldcatalog
                         Build layout setup
*& Report ZDEMO_ALVGRID                                               *
*& Example of a simple ALV Grid Report                                 *
*& The basic requirement for this demo is to display a number of       *
*& fields from the EKKO table.                                         *
REPORT zdemo_alvgrid                 .
TABLES:     ekko.
type-pools: slis.                                 "ALV Declarations
*Data Declaration
TYPES: BEGIN OF t_ekko,
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
statu TYPE ekpo-statu,
aedat TYPE ekpo-aedat,
matnr TYPE ekpo-matnr,
menge TYPE ekpo-menge,
meins TYPE ekpo-meins,
netpr TYPE ekpo-netpr,
peinh TYPE ekpo-peinh,
END OF t_ekko.
DATA: it_ekko TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_ekko TYPE t_ekko.
*ALV data declarations
data: fieldcatalog type slis_t_fieldcat_alv with header line,
      gd_tab_group type slis_t_sp_group_alv,
      gd_layout    type slis_layout_alv,
      gd_repid     like sy-repid.
*Start-of-selection.
START-OF-SELECTION.
perform data_retrieval.
perform build_fieldcatalog.
perform build_layout.
perform display_alv_report.
*&      Form BUILD_FIELDCATALOG
*       Build Fieldcatalog for ALV Report
form build_fieldcatalog.
* There are a number of ways to create a fieldcat.
* For the purpose of this example i will build the fieldcatalog manualy
* by populating the internal table fields individually and then
* appending the rows. This method can be the most time consuming but can
* also allow you more control of the final product.
* Beware though, you need to ensure that all fields required are
* populated. When using some of functionality available via ALV, such as
* total. You may need to provide more information than if you were
* simply displaying the result
*               I.e. Field type may be required in-order for
*                    the 'TOTAL' function to work.
fieldcatalog-fieldname   = 'EBELN'.
fieldcatalog-seltext_m   = 'Purchase Order'.
fieldcatalog-col_pos     = 0.
fieldcatalog-outputlen   = 10.
fieldcatalog-emphasize   = 'X'.
fieldcatalog-key         = 'X'.
* fieldcatalog-do_sum      = 'X'.
* fieldcatalog-no_zero     = 'X'.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'EBELP'.
fieldcatalog-seltext_m   = 'PO Item'.
fieldcatalog-col_pos     = 1.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'STATU'.
fieldcatalog-seltext_m   = 'Status'.
fieldcatalog-col_pos     = 2.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'AEDAT'.
fieldcatalog-seltext_m   = 'Item change date'.
fieldcatalog-col_pos     = 3.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'MATNR'.
fieldcatalog-seltext_m   = 'Material Number'.
fieldcatalog-col_pos     = 4.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'MENGE'.
fieldcatalog-seltext_m   = 'PO quantity'.
fieldcatalog-col_pos     = 5.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'MEINS'.
fieldcatalog-seltext_m   = 'Order Unit'.
fieldcatalog-col_pos     = 6.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'NETPR'.
fieldcatalog-seltext_m   = 'Net Price'.
fieldcatalog-col_pos     = 7.
fieldcatalog-outputlen   = 15.
fieldcatalog-do_sum      = 'X'.        "Display column total
fieldcatalog-datatype     = 'CURR'.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'PEINH'.
fieldcatalog-seltext_m   = 'Price Unit'.
fieldcatalog-col_pos     = 8.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
endform.                    " BUILD_FIELDCATALOG
*&      Form BUILD_LAYOUT
*       Build layout for ALV grid report
form build_layout.
gd_layout-no_input          = 'X'.
gd_layout-colwidth_optimize = 'X'.
gd_layout-totals_text       = 'Totals'(201).
* gd_layout-totals_only        = 'X'.
* gd_layout-f2code            = 'DISP'. "Sets fcode for when double
*                                         "click(press f2)
* gd_layout-zebra             = 'X'.
* gd_layout-group_change_edit = 'X'.
* gd_layout-header_text       = 'helllllo'.
endform.                    " BUILD_LAYOUT
*&      Form DISPLAY_ALV_REPORT
*       Display report using ALV grid
form display_alv_report.
gd_repid = sy-repid.
call function 'REUSE_ALV_GRID_DISPLAY'
       exporting
            i_callback_program      = gd_repid
*            i_callback_top_of_page   = 'TOP-OF-PAGE' "see FORM
*            i_callback_user_command = 'USER_COMMAND'
*            i_grid_title           = outtext
            is_layout               = gd_layout
            it_fieldcat             = fieldcatalog[]
*            it_special_groups       = gd_tabgroup
*            IT_EVENTS                = GT_XEVENTS
            i_save                  = 'X'
*            is_variant              = z_template
       tables
            t_outtab                = it_ekko
       exceptions
            program_error           = 1
            others                  = 2.
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
endform.                    " DISPLAY_ALV_REPORT
*&      Form DATA_RETRIEVAL
*       Retrieve data form EKPO table and populate itab it_ekko
form data_retrieval.
select ebeln ebelp statu aedat matnr menge meins netpr peinh
up to 10 rows
from ekpo
into table it_ekko.
endform.                    " DATA_RETRIEVAL

Security using custom field in PCUI

We would like to create a custom field on the header of the business partner to store information that would then be used in the security roles.
For example, we want to create a branch field on the header of the business partner and then use this field to restrict access to specific accounts within the sytem using a CRM Security role.
Does anyone know if you can use a custom field in the CRM system to restrict security within the PCUI application?
If anyone has any information, I would greatly appreciate it as we are on a crunch to get this implemented!
Thanks!

Hi Darcie,
If you add custom field and maintain value in it, i'm not sure if you can restrict access by CRM Security role.
If your users are going to be entirely based only on portal/pcui (i.e. they would not use SAP-GUI log-in) then you can consider the option of tweaking your Accounts advanced search and not letting users see certain accounts (based on the value in EEWB / custom field)
Hope this helps.
Regards,
Raviraj

F111 and payment method field 'payment orders only' deactivated T042ZL-XNOP

Hi
F111 gives an error for a payment method: "Creation of payment orders is not supported. Message no. PZ588.
Diagnosis
Payment method B is configured so that a payment order is created. This function is not supported in the payment program for payment requests. This payment method is not permitted here."
The cause is field 'payment orders only'T042ZL-XNOPO in FBZP of the payment method, which means no clearing of open items during payment run. Business reason for having this parameter activated: "As per the legal regulation in Poland, the vendor liability in your books cannot be cleared during Payment run. The vendor liability in your books can be cleared only after receiving confirmation from bank about the payment having been made to the vendors account.
Hence only Payment orders are created during SAP payment run ( no FI posting) ..The DME files generated are sent to the bank. After the confirmation is received from bank ( via the bank statements imported thru EBS) that the funds have been actually transferred to the vendor account, the vendor liability is cleared off form your books"
I do not want to use F110 because I do not want to use customers or vendors but I want to use GL accounts. Business is against creating a separate payment method with field 'payment orders only' T042ZL-XNOPO deactivated.
Any suggestion?

Since your requirement is with reference to GL accounts then F111 is the correct tcode. Payment request is created (trx RVND) and in this case can be processed only by SAPF111S via trx F111.
But to use tr. F111, a payment request should not contain a payment method, marked with "Payment order only" (tr. FBZP).
In your case it is correct that such an error PZ588 is generated since such payment methods are not supported by F111.
So please ensure that payment request may not contain a payment method, marked with "Payment order only".
Hope this information helps.
Kind Regards
Soumya

Is anyone successfully using Mobile Field service - laptop version in 12.2.X ?

We need this type of functionality but we are on 12.0.6. We are considering upgrading but we were going to upgrade later this year. However, we need this type of functionality as soon as possible. Is anyone using Mobile Field Service in 12.2.X with laptops?

Hardik,
I am using an O2 XDA II with Pocket PC 4.2. I am using IAS 9.0.4.0.0.
I have defined a service in my midtier which outputs XML with a signature box:
<SimpleFormItem name="p_signature" type="signature"> etc
My PDA displays the signature box correctly in the web browser.
When I sign the box and press Submit the following data items are returned to the midtier:
Query String: "sigSubmit=mySubmit&sig_width=200&sig_height=100&sig=&personName=tim"
Notice that the sig data is null.
I know that my IAS version is a little low, but, the problem appears to be that the plug-in in the browser is not returning any sig data.
Do I have an old version of the plug-in?
Have you used this plug-in?
Has it worked for you?
Do you know where I can get a newer version of this plug-in as it must work with Oracle Apps?
Regards,
Tim.

Payment on Account and dunning run

One of our customers demands some changes within the Business One.
The support in Ireland advised us to post these requirements in this Forum.
Payments on Account will not be considered in dunning runs.
The customers opinion is, that these Payments have to be considered in the dunning runs.

Hello Oliver,
in SAP Business One 2007 you may take the following types of docments into consideration when executing the dunning run (Step 4 - Document parameters):
- payments not based on invoice (payment on account)
- credit notes not based on invoice
- manual journal entries
Your customer's requirement is hence met.
All the best,
Kerstin

Allowing the field "Payment method supplement" to be changeable in FB02

Hi All,
I have a requirement which is to allow the field "Payment method supplement" to be changeable in FB02. It is currently not allowed for change. How will I make this changeable? Is customizing enough? Or program enhancement must be done? Please advise the steps to do this.
Thanks!

Hi
Please use tcode OB32 to make Payment method supplement field editable in FB02 transaction.
In the screen "Change view: Document change rules: overview: screen" click F5 or New entries.
In the subsequent screen enter * BSEG-UZAWE* in the Field Name and update all other fields like account type, transaction, company code.
Activate the Field can be changed check box and save.
Now after doing this change, when you try changing the document in FB02, the payment method supplement field can be changed.
Please update the fields Account type, transaction with relevant values.
Hope this will help you...
Regards,
Praisty

Need descriptions about field "Payment Details Defaulting Hierarchy"

Could someone provide us any information or documents about field "Payment Details Defaulting Hierarchy"
Resp RECEIVABLES
Menu: Configuration>Movements>Origins
Tab "Autoinvoice option"
A new field named "Payment Details Defaulting Hierarchy" could be filled with the following:
- Parent of Bill-To Customer
- Bill-To Customer
But what do they mean???
Need fonctionnal descriptions please!!
Best regards,
Johann

See the description of this field in Creating Transaction Sources Used For AutoInvoice and the Transactions Workbench [Video] [ID 1068008.1]
Sandeep Gandhi

Report using Parameter Field

Hi,
I have designed one report using Parameter Field which is Cost Code (string).
When I run my report, I ask to enter cost code. When I enter cost code 30, I get report for all transaction of cost code 30 and 300.
How could I avoid this problem.
Thanks
Mithani

Try with this
{Project_cost.EXPENSES_Code} IN {?Cost Code}
and also
Check the query formed after giving the input parameter. Goto Database --> Show Sql Query.

Can i use the same payment info on more than one iphone?

Can i use the same payment info on more than one iphone?

Contact iTunes Customer Service and request assistance
Use this Link > Apple Support iTunes Store Contact
Accepted forms of payment > http://support.apple.com/kb/HT5552

Use of field 'Payment Considered To' in Dunning Proposal (FPVA)

Similar Messages

Maybe you are looking for