Interface for open FI items to dunning agencies in ERP

Question

There is no SAP standard interface technology for sending out open FI items dunning data to a collection agency in normal SAP ERP solution. In standard only printing with SAPScript ( and Smartform ) is supported.
There must be tailored 'dunning interface to collection agency' customer solutions out there even for normal ERP accounts receivable, so what was your approach? All help are appreciated, but right now I am not looking for sample code, but rather overall best practises. Also I am aware, that each collection agencies have their own interfaces, but that can be solved with many options like EAI for example. Mostly I am interested how to get the dunning data created from standard dunning procedure regardless how the receiving dunning agency finally wants to have it.
I know that ERP-IS-Utilies has one solution, and I have even implemented that once, so you don't get points by refering to that. Unfortunately IS-U uses contract accounting and has a completely own dunning procedures (and own tables as well) compared to normal ERP dunning, thus no help for standard ERP dunning.
Br: Kim

Answer 1

crouchingchicken wrote:
I would set the File's Owner to by view controller and then I could drop a navigation item in and connect that right away to the controller
Yes, I agree. The nav item used to show up as an outlet of any view controller.
When I try to load the nib at runtime I get this error:
The problem with the doc is this line:
To push a new view controller at runtime, _create a new instance of your custom UIViewController subclass, initialize it with the nib_ file you created for it, and push it on the navigation controller stack.
The underlined portion can lead us to believe we can alloc and initWithNibName:bundle: as we would when File's Owner is a proxy for the controller we create in code. But that won't work in this case, since the controller we want is the one that's created from the view controller object when the nib is loaded. In other words, we don't want to alloc a new controller, we just want to grab the object made from the nib. Here's what to do:
// RootViewController.m
- (IBAction)nextView {
NSLog(@"nextView");
// SecondViewController *viewController = [[SecondViewController alloc]
// initWithNibName:@"SecondViewController" bundle:nil];
NSArray *nib = [[NSBundle mainBundle] loadNibNamed:@"SecondViewController"
owner:self options:nil];
NSLog(@"nib=%@", nib);
SecondViewController *viewController = [nib objectAtIndex:0];
[self.navigationController pushViewController:viewController animated:YES];
// [viewController release];
Be sure not to release the object obtained from the nib, since we didn't alloc it. Top level objects created from a nib are autoreleased. You can put some logging into the second view controller's dealloc to verify it gets dealloced when popped:
// SecondViewController.m
- (void)dealloc {
NSLog(@"dealloc: %@", self);
[super dealloc];
- Ray